And I despise supporting or troubleshooting Java applications.
Unfortunately that's my life these days.
From an admin perspective, python, php, hell.. Even ruby. All fine. But Java is a nightmare.
And I despise supporting or troubleshooting Java applications.
Unfortunately that's my life these days.
From an admin perspective, python, php, hell.. Even ruby. All fine. But Java is a nightmare.
FlightRecorder, single jar deployables, the JDK cli utils to get stacktraces and heap dumps etc are good.
No npm getting a zillion files. Just get some jvm, point it at your jar and done.
If you are talking 2001 servlet container and so on, sure terrible, but if you are running those, switch jobs, thats not java's fault.
Curious about what's so hard about Java.
Er, that’s kind of the point of the Java Virtual Machine… It keeps you from tying your application to a particular system architecture.
I’ve noticed that JVM administration tends to fall into the “no man’s land” between devs and admins: Devs figure that the Admins will take care of it, and Admins are annoyed that they need to use a separate set of tools to admin the Java apps (and are not eager to learn them.)
It is working on one server and then broke on a newly built server apparently due to some network settings which devs/ app admins are not aware of.