3 ms·
I mostly agree except the Java part. AFAIK Java (at least J2SE) has been very stable with backwards compatibility going back to the 90s.
by Crinus 7y ago
I mostly agree except the Java part. AFAIK Java (at least J2SE) has been very stable with backwards compatibility going back to the 90s.
- DannyB2 7y agoFurthermore, you can package a JDK or JRE with the application, such that the application uses the packaged JDK/JRE, and ignores any that may be installed on the OS. JDK/JRE's are open source, and binaries are available from AdoptOpenJDK, Red Hat, Azul Zulu, and others. "Maintenance" might be to simply swap out one JDK with a newer one and then make sure the app still works -- which it should. But there ARE some ancient things in Java that are being deprecated. Or moved out to separate libraries not bundled into the JRE. I would also point out that with Docker you could package every possible dependency into the container. The container is now portable and has no dependencies outside of what is packaged in the container. To the user, they don't care what technology or Rube-Goldberg contraptions exist within the container. Also see AppImage.
- mamcx 7y agoIs similar with .NET and other environments (C++, js), where is possible to get his metric IF you know what you are doing. But the ecosystem push harder away from this.
- altmind 7y agojava had: * bundled xerces around 1.6, breaking apps that also carried their own xerces * removed sun.misc.Unsafe from v11, breaking legit apps the apps that use off-heap memory * sun and later oracle made everything to make applets useless, creating ridiculous security requirements and no clear way for a user to whitelist trusted applets. same for java web start. they had no problem disabling MD5 and RSA in their SSL impl, breaking the old clients.