2 ms·
Sure the APIs are gone, but you can still compile the code and include the libraries from those APIs and still run the dang thing. Also, the removal of those AP
by foxyv 3y ago
Sure the APIs are gone, but you can still compile the code and include the libraries from those APIs and still run the dang thing. Also, the removal of those APIs was done in an extremely responsible manner with long periods of deprecation. Most of those APIs were deprecated in Java 5 anyways.
- pjmlp 3y agoNo you cannot, because some of those APIs depend on native code that is now gone like in Thread.stop(). It doesn't change the fact that Java 4 using those features won't run anylonger without additional effort. Another are that has occasionally had breaking changes were JDBC drivers and related interfaces. Java folks try to minimize breaking changes, yet each release has a section about breaking changes for a reason, throughout Java's history.
- foxyv 3y agoIf you are using obscure features then yeah, you are going to see breaking changes. Just try running Tomcat 7 on Java 8+. But there will always be exceptions like that in any language. Just like Rust has safety guarantees, until you start using "unsafe." But, I have applications that were coded in the 90s that are still running fine on Java 17 with minimal maintenance for security updates. No trans-piling necessary. I don't know about these "Java Folks" but no one is claiming that Java is a magic unicorn. But it is a well designed language that has excellent backwards compatibility.