8 ms·

I mean, what is old? How far along are frameworks these days, and what are companies using? That team was using Java 17. Java 21 was just released and framewor

I mean, what is old? How far along are frameworks these days, and what are companies using? That team was using Java 17. Java 21 was just released and frameworks had no meaningful support for virtual threads whatsoever. In my experience, most companies using Java are chronically multiple versions behind (e.g. some of my friends still in the Java world are on 11). Perhaps you can share some sources which prove that Java's performance blows Go out of the water without breaking a sweat? I have not seen any such articles about that in the past 3 years, besides the cherry-picked cases where the JVM JIT can optimize some small algorithmic part of the program on the fly (which is not relevant in most web applications). I'm happy to stand corrected. Edit: I found this one using a quick search myself https://medium.com/@mohnisha/java-vs-golang-performance-testing-4d0d6a5123fb https://medium.com/@mohnisha/java-vs-golang-performance-test... I'll check it out and see if I can reproduce it myself too. Still too bad about that gargantuan memory usage, but I guess memory in the cloud is cheap.

hocuspocus 7mo ago
> Java 21 was just released and frameworks had no meaningful support for virtual threads whatsoever. Spring was ready on day 1, as virtual threads had been an experimental feature since Java 19. Spring Boot added support within a couple months. > In my experience, most companies using Java are chronically multiple versions behind (e.g. some of my friends still in the Java world are on 11). And that's on you.
- Capricorn2481 7mo ago
  >> In my experience, most companies using Java are chronically multiple versions behind (e.g. some of my friends still in the Java world are on 11). > And that's on you What most companies do is on them?
- HendrikHensen 7mo ago
  > And that's on you. Sorry I have to defend my pride here a little bit. When I joined my previous company, the entire company was on Java 8. When I left every app in every team there was up-to-date on the latest LTS release at the time, 17. I assisted many teams in upgrading their Java, Spring, etc, and inspired even more. I would argue that I'm one of the last people who you could blame for most companies being many Java versions behind...
  - hocuspocus 7mo ago
    So what's the issue then? You'd be able to bring other teams to current versions of Java and frameworks, which have all been using virtual threads for the past 3 years.

hocuspocus 7mo ago

> Java 21 was just released and frameworks had no meaningful support for virtual threads whatsoever. Spring was ready on day 1, as virtual threads had been an experimental feature since Java 19. Spring Boot added support within a couple months. > In my experience, most companies using Java are chronically multiple versions behind (e.g. some of my friends still in the Java world are on 11). And that's on you.

Capricorn2481 7mo ago
>> In my experience, most companies using Java are chronically multiple versions behind (e.g. some of my friends still in the Java world are on 11). > And that's on you What most companies do is on them?
HendrikHensen 7mo ago
> And that's on you. Sorry I have to defend my pride here a little bit. When I joined my previous company, the entire company was on Java 8. When I left every app in every team there was up-to-date on the latest LTS release at the time, 17. I assisted many teams in upgrading their Java, Spring, etc, and inspired even more. I would argue that I'm one of the last people who you could blame for most companies being many Java versions behind...
- hocuspocus 7mo ago
  So what's the issue then? You'd be able to bring other teams to current versions of Java and frameworks, which have all been using virtual threads for the past 3 years.