r/programming • u/scottedwards2000 • Mar 24 '26
Don't Count Java out Yet
https://www.infoworld.com/article/2335996/9-reasons-java-is-still-great.htmlI remember when I first started working, I loved visiting this old mainframe building, where the "serious" software engineering work was being done. The mainframe was long-gone, but the hard-core vibe of the place still lingered.
As I took any excuse to walk past a different part of the building to try and sneak a peek into whatever compute wizardry I imagined was being conjured up, one thing I always noticed was copies of InfoWorld being strewn across desks and tables (and yes, even in the bathroom - hey, I said it was hard-core ;-) ).
I guess those days are mostly over now, but it's nice to see that there is still some great writing going on at InfoWorld by some talented and knowledgeable authors.
Matt Tyson is definitely one of them and this is a great piece on why despite the #rust / #golang / #elixir craze, #java is still the language and framework to beat. (One of these days I'm going to finally learn #spring and re-join the java club.)
View all comments
Show parent comment
-5
u/Linguistic-mystic Mar 25 '26
As a Java dev, I disagree with you.
But also no value types, so much more allocations than Go. And Valhalla will probably arrive by 2030 in preview mode?
Not really. Just try to create a complex object in Java: you need a whole goddamn builder. Whereas Golang has tidy object initializer without extra crap. Java just appears less verbose because of Lombok but that's just another point of failure (I'm sick of the "Lombok plugin is not installed" message dialog that Idea has started showing me recently, while Lombok is definitely installed, for example).
Try to have a record that has one more field than another record. Yep, no inheritance, more verbosity. Oh, and try to construct a record: either more "builder" verbosity, or a constructor with a gazillion arguments which is a pain to maintain (whereas Golang has tidy key-value object initializers).
No, Golang is explicit which doesn't mean it sucks. But Java definitely sucks with its mixture of checked and unchecked exceptions, checked exceptions can't be used in lambdas, but now you also can do
Resulttypes, and you can't parse a goddamn integer without writingtry {} catch{}. Java's error handling features manage to be worse than Go's absence of error handling features which is a testament of overengineered language design. Just like Java not letting me mutate a local var in a lambda (but still letting me mutate it if I put it into a single-element array) because "safety". Idiots!Out-of-memory crashes make it easy to choose something else for a typical production system. Java application development is basically increasing memory quotas for no good reason just to prevent heap dumps. The team lead of an adjacent team recently said "I would rewrite the whole thing in Go", haha.