I get it, you have no idea what trying to optimize around an ever-changing JIT recompiler looks like
Comment on An After-School Program Teaches Teens Java and Python
Fades@lemmy.world 11 months agoWe get it, you have no idea what modern Java looks like
pivot_root@lemmy.world 11 months ago
AeroLemming@lemm.ee 11 months ago
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.
kaffiene@lemmy.world 11 months ago
It looks like something that doesn’t happen
Valmond@lemmy.mindoki.com 11 months ago
Found the guy thinking java can be as fast as C/C++
pivot_root@lemmy.world 11 months ago
The just-in-time compiler isn’t bad, but the rest of it is. An optimized hot loop has the potential to emit better instructions than a C/C++ compiler not using PGO, but you’re never going to see that in any real workload.
If you could rip out/avoid the garbage collector, give it the ability to use escape analysis to avoid heap-allocating every single object, and prevent it from implicitly making every function virtual, then maybe. But at that point, you might as well just a different language.
Valmond@lemmy.mindoki.com 11 months ago
Ha I love it when I’m right 😁😉
____@infosec.pub 11 months ago
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.
pivot_root@lemmy.world 11 months ago
BrianTheeBiscuiteer@lemmy.world 11 months ago
I don’t know a single language that’s immune to the things you just mentioned.
stardreamer@lemmy.blahaj.zone 11 months ago
Haskell is still as beautiful as the day it was first made.
Except for class methods. We don’t talk about methods.