4 ms·
A bit cheeky that they do this at a time when moving on is particularly expensive. Nobody would have had issues with this sort of behaviour between 6 and 7, or
by toyg 9y ago
A bit cheeky that they do this at a time when moving on is particularly expensive. Nobody would have had issues with this sort of behaviour between 6 and 7, or even 7 and 8, because backward compatibility was massive. From what I understand, that's not exactly the case with 9.
- LudoA 9y agoPretty sure that Java 9 should still fully support apps written for older versions of Java. However, apps written specifically for Java 9 (e.g. using the new modules system) wouldn't work on older versions of Java.
- tragic 9y agoIt's a little more complicated than that; for example, a good many clojure libraries were broken by Java 9. I haven't been writing clojure day to day for about six months, so I don't know how things are looking just now. But it would be a non trivial task to migrate a lot of clojure apps over.
- dantiberian 9y agoI don’t think that many libraries were broken by Java 9. There was a bit of tooling, and ClojureScript required adding a module, but I haven’t come across any major broken libs yet. Let me know if you have examples I can add to my Clojure Java 9 upgrade guide: https://www.deps.co/blog/how-to-upgrade-clojure-projects-to-use-java-9/ https://www.deps.co/blog/how-to-upgrade-clojure-projects-to-...