Re:Java at 30: The Genius Behind the Code That Changed Tech
by fpoling on Friday May 16, 2025 @04:24PM
(#44009493)
Java version updates typically change GC behavior. If one has highly tuned setup there is no guarantee that a newer version would not regress.
Another problem is crashes. Java runtime is highly reliable, but still bugs happens.
Re:Java at 30: The Genius Behind the Code That Changed Tech
by Pet_Ant on Friday May 16, 2025 @08:07PM
(#44010910)
Are you talking about performance or behaviour? I’ve never seen an issue caused by a GC.
Re:Java at 30: The Genius Behind the Code That Changed Tech
by fpoling on Saturday May 17, 2025 @04:15AM
(#44012852)
Latency spikes are the issue. Modern Java mostly solved this, but tuning GC settings is still the thing especially when Java runs on a big server.
Re:Java at 30: The Genius Behind the Code That Changed Tech
by josefx on Saturday May 17, 2025 @06:04AM
(#44013254)
It is "mostly" backwards compatible. Applets and everything related to them where dropped. A few interface dependencies where changed to improve modularity of the runtime. Widely used hacks like sun.misc.unsafe are getting replaced with official APIs and locked down. Development of some Java EE packages has been taken over by a third party, so they are no longer packaged within the java namespace. To name just a few of the bigger examples.
It always made me wonder why I hear about companies who are running very old versions of Java though. It always seemed like backwards compatibility would make keeping up to date with the latest an almost automatic thing.