I know exactly what modern Java looks like, and it could be beautiful. But… legacy cruft and lazy devs make it painful. And tech debt, let’s be honest.
I’d view a greenfield project rather differently, but those are unicorns.
I think if your project is so performance-critical that small runtime changes can cause performance issues, Java (or any other garbage-collected language) isn’t a good choice. That’s not the case for the vast majority of projects.
Back when I was in school, corporal punishment was the norm. I would still prefer that over Java.
We get it, you have no idea what modern Java looks like
I know exactly what modern Java looks like, and it could be beautiful. But… legacy cruft and lazy devs make it painful. And tech debt, let’s be honest.
I’d view a greenfield project rather differently, but those are unicorns.
I don’t know a single language that’s immune to the things you just mentioned.
Haskell is still as beautiful as the day it was first made.
Except for class methods. We don’t talk about methods.
I get it, you have no idea what trying to optimize around an ever-changing JIT recompiler looks like
I think if your project is so performance-critical that small runtime changes can cause performance issues, Java (or any other garbage-collected language) isn’t a good choice. That’s not the case for the vast majority of projects.
It looks like something that doesn’t happen
Found the guy thinking java can be as fast as C/C++