9 is considered broken because there's a compiler bug https://bugs.openjdk.java.net/browse/JDK-8204322 , in general I believe oracle has killed java with it's 6 months release cycle as they want to monetize it on as much as possible. 9 was never meant for production use, but as a whip to get companies to buy LTS for java 8, (you don't spend years working on something only to kill 6 months after it got out)
I always refer to this mail item in Cassandra's list as to the problems commercial companies would be facing. https://lists.apache.org/thread.html/8a24e6b88309601cf36710a6e7bc011ed98b7a2b1f76ac969b86a26e@%3Cdev.cassandra.apache.org%3E This would escalate to other open source projects as developers will attempt to race making the project compatible with coming versions. I mean even today java isn't exactly growing in popularity, but forcing companies to pay oracle's premium prices for it, would drastically change the way management will view it, as they will opt for a accessible products. the only way for java to remain as it is, is if adoptOpenJDK will be strongly and heavily supported, and even that is questionable. -----Original Message----- From: Fabrice Bacchella <fabrice.bacche...@orange.fr> Sent: Wednesday, October 03, 2018 10:10 AM To: Maayan, Elhanan <elhanan.maa...@sbdinc.com> Cc: Frank Fock <f...@agentpp.com>; Jeremy Norris <ishmae...@gmail.com>; snmp4j@agentpp.org Subject: Re: [SNMP4J] Java9+ required now? *External Message, please be cautious.* > 3. java 9 itself is considered broken, eol, and on top of that migrating to > it , extremely problematic , I suspect many organizations won't go for it due > to those reasons. > Java9 is EOL, migration to it can be difficult, but can also be easy, depending of your code. But I'm not sure we can call it broken. But don't except the situation to improve. J9 was difficult because it introduce many new things that will not go away in latter versions. So if you're afraid to migrate to Java9, you're stuck forever in J8, as the problems will be the same in J11 (the next LTS release). A little like switching from Python 2 to Python 3. _______________________________________________ SNMP4J mailing list SNMP4J@agentpp.org https://oosnmp.net/mailman/listinfo/snmp4j
