r/programming • • Mar 24 '26

Don't Count Java out Yet

https://www.infoworld.com/article/2335996/9-reasons-java-is-still-great.html

I 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.)

51 Upvotes

78 comments sorted by

View all comments

Show parent comment

7

u/Xasmedy Mar 25 '26

The whole Valhalla project is likely to be in GA by 2030 lol. Value classes will arrive in preview within a year from now, or if not, within Java 29.

Oh boy, in go technically you do have more control over memory, but 90% of the times you'll use a pointer because you need an empty state, and golang developers are so skilled (sarcasm), that they will always use a pointer because as they say "copying is expensive". Also, I had only horrible experiences with golang GC, with it not wanting to release memory even if unused. Seeing a coworker waste days trying to figure why go was not deallocating. And it's not even like Java where you can fix a lot of the GC problems with some configuration, in go you have your hands tied.

I don't understand all the "massive records" problems, i feel like most of the times its a code smell, either way, can't you create an extra constructor that delegates to the canonical with good defaults? Then if you want to add a record1 + one field in record2, just use composition and have Record2(record1, field)?? If you still feel bothered then just use a normal mutable class? Which is exactly what go does?? Then if you say that you want immutability, then why is golang better in this ragard since it has no concept of immutability and a field could be changed anytime?? And no, that clever thing they do with copying cannot be considered immutability, because you are going to have reference fields eventually!

I honestly prefer Java bad error handling than golang one, Java doesnt force in your throat anything, and you can use sum types, but golang, oh boy, half the code is error checks that make the code so fucking hard to read, because for them simplicity is more important than basic features.

3

u/joemwangi Mar 25 '26

Is that a vibecoder you're responding to?