4 ms·
Thats not a JVM, but an application/library level issue. The JVM ABI has been stable for quite some time.
by martontoth 6y ago
Thats not a JVM, but an application/library level issue. The JVM ABI has been stable for quite some time.
- reader_mode 6y agoI see limited value in that when JVM ships with frameworks which break compatibility regularly - I doubt Python packages which had no dependencies on core libraries had any problems using 2to3 to migrate.
- overtomanu 6y agocan you give examples?
- pjmlp 6y agoOther than a few breaking changes in JDBC, there was hardly any other breaking change in the standard library. And modules was a single breaking change, hardly a regular thing.
- toast0 6y agoWhat's the difference? I still can't run my existing jar with a new JVM package; so the new JVM package isn't compatible with old binaries. And I have to horde old installers if I want specific programs to work (thankfully, I only have one or maybe two Java programs I'd like to run)