3 ms·
The JVM itself makes backwards incompatible changes. I have jars that work on earlier VMs, but don't anymore.
by monocasa 7y ago
The JVM itself makes backwards incompatible changes. I have jars that work on earlier VMs, but don't anymore.
- yarg 7y agoSure, but I'm damned certain that's never happened with the destruction of interoperability being the goal in mind.
- monocasa 7y agoThe destruction of interoperability wasn't the goal in mind with Android either. Java ME sucked, and SE is somehow even a worse fit for phones. The fundamental process model destroys battery life, hence the switch in Android to that model that'll shut the app down basically at any time and allow it to save state, so it can come back to where it was later. In addition to that, an IPC system was added (which basically doesn't exist in Java ME), and a bunch of support for devices that are only accessible in Java via 3rd party libraries anyway. Oh, and the lack of swing. But come on, even Eclipse doesn't use swing.
- sliken 7y agoHaving jars only work with specific oracle JVM versions is not at all unusual.
- vageli 7y ago> Having jars only work with specific oracle JVM versions is not at all unusual. I think that underscores the point? That even legitimate JVM versions were not substitutable for each other.