4 ms·

>Adoptium is not involved in OpenJDK They replace adoptOpenJDK https://adoptopenjdk.net/ https://adoptopenjdk.net/ ... >By "terrifying license change" you mea

>Adoptium is not involved in OpenJDK They replace adoptOpenJDK https://adoptopenjdk.net/ https://adoptopenjdk.net/ ... >By "terrifying license change" you mean the 100% open-sourcing of the JDK, and making it 100% open and free No, I mean https://www.policypak.com/resources/pp-blog/oracle-java-license-change/ https://www.policypak.com/resources/pp-blog/oracle-java-lice... >Once again, whatever we did 8 years ago I didnt (particularily) place any blame. If it wasnt your testing that was catching them early it must have been someone elses. Presumably they left the ecosystem. >the JDK is completely open. But a shadow of its former self. >but we don't have more bugs than before Im really talking about issues related to very long running jvms. The kind of things that would have killed applications like apache tomcat dead. In fact it looks like they use their own jvm build now, I'll give that a go at the same time..... however it looks they they are still really on 8 as well.

pron 5y ago
> They replace adoptOpenJDK https://adoptopenjdk.net/ https://adoptopenjdk.net/ ... Yep, it's the same IBM team, who aren't involved in OpenJDK (and weren't when they were called AdoptOpenJDK). They mostly know OpenJ9. > https://www.policypak.com/resources/pp-blog/oracle-java-lice https://www.policypak.com/resources/pp-blog/oracle-java-lice... Almost everything here is wrong. The prices and licensing terms are very wrong, but, most importantly, what Oracle did was, instead of provide one part-free, part-paid, JDK, we started providing two indentical ones with different licenses: one completely free, and one for support subscribers. > But a shadow of its former self. Actually, it has many more features today than it did back in 8.