646
1 hour in Java
(piefed.jeena.net)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 17 Aug 2024
646 points (95.5% liked)
Programmer Humor
32410 readers
325 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
But one compiling error is Java is 7 run time errors in python.
There is a type error and you couldn't have known it beforehand? Thanks for nothing
I will confess that I get a sense of psychological comfort from strict typing, even though everyone agrees Python is faster for a quick hack. I usually go with Haskell for quick stuff.
And then the quick hack gets a permanent solution and the next employee has to fight trough the spagetti.
sounds like not my problem
You will find yourself being that next person when you haven’t touched the code for a week and come back to add something and are like wtf.
The circle of 1!f€
This may be true, but it's equally true in any programming language, so not really relevant.
I'd guess it's less true for something statically typed, just because that reduces the ways it can be unintuitive.
I firmly believe that every language has an equal proportion of spaghetti code to clean code. The only factor that might screw with this is how much a language is used in industry, which I'd expect raises the ratio. However, there's plenty of hobbyists writing spaghetti code too so I don't think even that factor has much effect.
Really? Doesn't that imply non-spaghetti brainfuck or assembly?
Okay, I'll grant you brainfuck... As for assembly, I don't think it's inherently spaghetti. You can split it up into functions just like you can with an actual programming language. It's not impossible to make structured code.
That said, I never coded assembly outside of a mandatory university course, so I don't feel super confident in saying that. But I don't think of it as a programming language anyway - it's a 1:1 translation to/from machine code, and machine code isn't meant to make programming easy or scalable.
And TBF neither is brainfuck. It was a bit of a cheeky example, but I wanted to really emphasise the range of differences between languages, and language-like things.
I have trouble believing that every language is exactly as easy to organise code in. I'll give you that it's possible in every language (and assembly) to organise code, but that's far too low a bar for practical measurement. Technically you can dig a ditch with a rusty spoon, too...
If Roller Coaster Tycoon had well organised code, that was down to way more effort being expended to make it that way.
Oh, and if you really want a tough language, try Malbolge. The ratio of structured code to spaghetti code in that one is 0:1 - there are 0 instances of non-spaghetti code, and 1 instance of spaghetti code. I refuse to believe there's any more code other than the Hello World example.
You know, it must have taken some balls to publicly release a compiler you can't even test yourself.
I think we're going to have to agree to disagree. If any project in any language has well-organized code, it's down to a ton of effort.
Assembly is harder to code in, period. It's even harder when your code is a total mess and you didn't plan ahead. For a large assembly project to survive at all, some structure is as necessary as oxygen. And not to mention, there are far fewer projects written in assembly anyway.
Such is life.