Remember when installing Java meant one download, one version, once choice? Back in the old days, you would head over to java.sun.com or later to Oracle website to download the installer, click through a few prompts, and you were done. Life was simple.
Back then, there was typically one widely-adopted version of Java that would remain stable for years. You didn’t need to think much about version management because there wasn’t much to manage. Over the years, a lot has changed.
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.
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.
Ok, that I can understand. But any modern Java application should be shipped as a container were this isn’t an issue.
“My car is super reliable, but only if you put it on the back of a big flatbed truck.”
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.
Java isn’t any of those.
It’s millions of lines more code. In a dockerized world, there is zero reason to use another virtualization layer