c/hackernews · by rssbot@lemmy.bestiver.se · 267dInstalling Java in 2025, and Version Managers https://blog.hakanserce.com/post/version_managers/Comments 12 points · 8 comments · view on lemmy.world
8 Comments
orbituary@lemmy.dbzer0.com · 6 pts · 267d
...but one thing remains the same: it still sucks.
AudaciousArmadillo@piefed.blahaj.zone · 5 pts · 267d
Not sure what experience with Java you are talking about. As a Dev, modern Java still rock solid and is finally quite convenient to use and the JVM itself is a great runtime.
orbituary@lemmy.dbzer0.com · 7 pts · 267d
As an admin who has to update it, work with it, or interact with it from a workstation or server, it's a terrible experience.
AudaciousArmadillo@piefed.blahaj.zone · 2 pts · 267d
Ok, that I can understand. But any modern Java application should be shipped as a container were this isn't an issue.
orbituary@lemmy.dbzer0.com · 4 pts · 267d
"My car is super reliable, but only if you put it on the back of a big flatbed truck."
AudaciousArmadillo@piefed.blahaj.zone · 2 pts · 267d
I don't see how you'd have any less problems with a natively installed Node.js, Python or PHP application. This is not a Java specific issue.
orbituary@lemmy.dbzer0.com · 3 pts · 267d
Java isn't any of those.
Deifyed@lemmy.ml · 3 pts · 267d
It's millions of lines more code. In a dockerized world, there is zero reason to use another virtualization layer