Oracle:
Hey everyone remember when we invented Java and it was secure and then we kept adding badly thought out features until it became terribly insecure
well we're doing that again only 10x faster so all good bro
also we're fixing browser security by taking it completely out of the browser
hope you enjoy
https://jaxenter.com/java-10-interview-series-part-4-143144.html
<< Greg Luck: Yes, it is too much. The community only wants a new version of Java every 3-4 years.
Oracle is speeding up Java releases combined with reducing the support period for these new releases unless you are a customer of theirs. Java 9 and Java 10 are only supported for 6 months! So, Java 9 is now unsupported as of March 2018!!>>
<<Why would you use a version of Java you cannot get new updates for? Java 9 and Java 10 should be considered beta versions from a production standpoint.>>
<<And the jury is out on Java 11. If Oracle aggressively pursues monetization from Java, then Java 11 will have a short public (free) maintenance window, then it too will be considered non-production.
I think almost the entire Java user base is going to stay with Java 8 and await Oracle’s final position on all this after their monetization strategy plays out. We will likely be waiting a few years more on this.>>
Even the Java developers on Reddit are only slowly realising just how much trouble they're in.
https://www.reddit.com/r/java/comments/870xbv/java_11_jdk_roadmap_the_new_features_you_can/
<< We are just moving to JDK8. Anything later is just pie-in-the-sky for us right now.>>
<<My stack doesn't even run on Java 9 thanks to internal classes being hidden. Still waiting for some 3rd-party components to be updated...>>
That sound is the wheels, on fire, flying off and landing in a chicken coop
I feel like this whole thing is being driven entirely by the "cloud" end - ie, bespoke Java software done inhouse and on own servers, offering web services - with ZERO THOUGHT to people who run Java as *clients*.
And even then, zero thought given to support for even IDEs, let alone old existing code which 9,10,11+ is breaking spectacularly.
@natecull
I can't completely figure out Java's failure mode, but it seems like a more extreme case of a pretty common one -- one that has afflicted Oracle's everything for years.
I suspect it has something to do with Java initially being learned only by people who only learned to code for business reasons, who in turn only learned Java, and then those people being put in charge of designing new versions of Java.
@natecull
It's like watching the soviet union collapse, except that nobody gets 'liberated' because all the competitors are collapsing the same way at roughly the same time for the same reasons.