The company I was working for at the time spent a not insignificant amount of money and effort migrating away from Oracle JDK when they first pulled this shit.<p>It was a B2B outfit, had maybe 30 customers running a dozen different products that the customers hosted themselves. The product was critical to business and the customers were large and part of critical infrastructure. Even a short outage would have made it into the news. What I'm saying is it wasn't a place where you could just hope for the best while migrating JVMs, everything needed to be tested and re-tested from every imaginable angle.<p>This was extremely expensive, but in the long run, it was still a lot cheaper than ponying up for oracle licensing costs.<p>I don't work there anymore, but I doubt they are repeating the process to migrate back, especially given how well OpenJDK works.
It seems they were not in a dominant position in terms of market share. Anyone have a clue how low Oracle's market share was?<p>"Surveys suggest that Oracle's JDK distributions are not the most popular Java distributions anymore. Developers seem to prefer OpenJDK distributions from AdoptOpenJDK (now Eclipse Temurin), Amazon, Microsoft, Azul, and other vendors. These organizations also provide commercial support for their distributions. In the case of Eclipse Temurin, Azul offers such support."
For most companies, unless you haven’t switched already, I assume this won’t matter. Why switch back from Azul or whatever unless there’s a strong reason to? Nothing is preventing Oracle from trying to monetize their JDK aggressively again.
Fuck them, that's what I have to say.<p>And also thank you, for giving many companies the necessary push for them to realize Oracle's JDK was not the only game in town and many others could deliver a perfectly fine JDK.<p>There are few things worse in this business than being labeled an "unreliable partner" and Oracle is being seen as just that even at big companies. Oracle's wisdom to pull this kind of bullshit is already legendary, the Open Solaris train-wreck, the MySQL writing on the wall, the OpenOffice implosion, the JDK shoot-in-foot, those samurais at Oracle's board sure know what they're doing..
Guess it didn't work well for that. Thankfully projects like AdoptOpenJDK exist, so there are basically zero reasons to touch their stuff ever again.
I actually thought Oracle's move initially was actually a good thing: It brought some much-needed diversity to OpenJDK builds.<p>Very pleased to see this move as well. It's taken a very very long time, but it's encouraging to see Oracle finally understand the open source ecosystem.
From the article -- <i>Providing Oracle OpenJDK builds under the GPL was highly welcomed, but feedback from developers, academia, and enterprises was that they wanted the trusted, rock-solid Oracle JDK under an unambiguously free terms license, too. Oracle appreciates the feedback from the developer ecosystem and are pleased to announce that as of Java 17 we are delivering on exactly that request.</i><p>Translation, everyone stopped using our stuff in favor of the GPL version, that sucked so we changed the terms on ours to be free for commercial use. I bet they collect data and resell it but that is just a guess.
Why would anyone talk them seriously again.<p>Thay did this same thing with OpenOffice.<p>At the rate things are going, MySQL would also get this in the next 10yrs.<p>Oracle wants to extra as much resources as possible from any product. And when they realise the tech world has moved on, would try to throw a hinge to the wheel.
There are many other good JDKs out there, and with Oracle changing their license back and forth like a pendulum, I can not stress enough that going with the Oracle JDK should be considered a bad idea. See <a href="http://whichjdk.com/" rel="nofollow">http://whichjdk.com/</a> for further detail (was posted here a couple of months ago)
Oracle has been doing amazing work for OpenJDK and Java, it’s just that Oracle’s JDK isn’t a great business model. Glad that they realized that too and I hope it doesn’t stop them from putting resources behind it.
I guess Oracle saw that enough orgs were opting out of JDK 17 adoption?<p>They'll have to boil the kettle much slower, like Microsoft and Apple do.
Still a shitty license:<p>> [For LTS Oracle JDK versions] security updates will be available for a total of three years. After that period, further use of the Oracle JDK in production requires a commercial license.<p>Apparently the business model is having commercial customers deploy Oracle JDK and suing them as soon as they forget to upgrade after three years.
Yeah, right. As if I'm ever going to allow anything Java-related on anything I manage again.<p>"This application requires JRE #" -- end-user Googles JRE # and downloads/installs it.<p>End-user organization gets sued by Oracle lawyers for 10K site licenses for JRE #. Sure, they COULD have downloaded OpenFerretMongrelAsphalt JRE Pi, but yet, here we are...
The longstanding disaster of Java version numbering and licensing continues. How long until they reverse course on this? I don’t know of any other popular language with a such a sordid history in these areas.