Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Switched jobs a year ago, now I write software to process financial data exclusively in Java. Used to write userland 802.11 parsers/generators in c/c++. I can honestly say that the memory considerations are pretty much the same at the end of the day, just don’t have much control over when memory gets freed. Stop the world gc pauses typically show up in code that already has poor memory management. Still some concept of mechanical sympathy required to play. I have a feeling a lot of the complaints come from people that don’t know much about memory management in general
-
@JustThat Java 11 is the latest LTS release until 17 rolls out in September. Most places just don't bother with the intermediate releases, no-one wants to be upgrading every 6 months.
And sure, course it doesn't - though any new pre-Java 8 work would be madness in this day and age imho. But either way, this is a new project that *is* being done in Java 11, by devs who really should know better.
I get it, Java is an old language that's verbose as the day is long. But damn, please don't make it *even more verbose* than it needs to be. We've got the tools now to make it at least somewhat tolerable.
I mean, come on, we've got lombok, we've got streams, and we've had Comparator.comparing since Java 8. That's the best part of a decade you've had the luxury of writing single line comparator implementations out the box, but noooo, certain people have to pretend they're stuck in the 90's by thinking these multiple if / else statements are somehow still the best way of doing things.
Dahhh. Skill up people. This is not an industry where you can just do everything how you did it 20 years ago and call it good.
rant