4 ms·
That seems like a mistake, but it's very problematic if true. Having to go through a grueling JVM version update every 3 years, or more often if you can't jump
by phendrenad2 5y ago
That seems like a mistake, but it's very problematic if true. Having to go through a grueling JVM version update every 3 years, or more often if you can't jump 3 years worth of JVM updates at once? Brutal.
- kaba0 5y ago> grueling JVM version update Since when is it grueling? 8->9 was slightly hard, but mostly due to old dependencies doing shit with sun.misc.*, they shouldn’t have and it took time to update them. But even a Java 1.1 class file will run just fine on Java 17, and with the strong encapsulation enabled in recent versions, no hard update will come again (as the internals are not reachable from code, they are free to change)