Ask questions and see you at May, 13th (this time one week later), 6.PM. CET: http://www.ustream.tv/channel/adambien
Also checkout recent episode:
Please keep the questions Java EE-stic. Means: as short and as concise as only possible. Feel free to ask several, shorter questions.
Dates for (cloudy) winter 2019 airhacks.com are available.
Hi Adam, as freelancer myself currently i am very concern about state of commercial support for different versions of JDKs from different vendors.
JUG Dortmund Lead, Java Champion, JavaOne Rockstar Hendrik Ebbers has given a talk at local meetup group in Nuremberg about changes in Oracle JDK license subscription program.
So he explained that if three major JDK Vendors find a bug in their commercial JDK version they fixed and commit the patch to own private version source control and then if they suppose to commit to openJdk this probably can cause an issue, because different JDK Vendors have different release cycles.
Lets just imagine following situation:
Vendor A find a bug in own commercial JDK 17th and fix it and commit it for version 18 of openJDK and at the same time Vendor B find the bug in version 18 and released the commit to openJDK 19 and at the same time Vendor C find a bug and fix it and released it in openJDK20 and lets suppose that the bug which was fixed by all the vendors is one and the same, then it's obvious question who will decide which of the patches is a right and appropriate one for the openJDK?
Sure for commercial clients which use the commercial version of Java JDK of one or another Vendor its ok, but what about middle size enterprises and start up company's, i know for the fact ,that this can probably caused a financial damage (switching to commercial version of jdk) to such company's, i decided to recommend to my client's to slowly switch and use https://adoptopenjdk.net/ because its really free and include all fixes which will be found by RedHat i mean by IBM. This is not ideal situation for JDK as platform, because adoptopenjdk does not have a TCK approval of standard.
So what is you opinion about such fragile Java Platform state, what kind of advise we should give our clients late in the future? I sincerely hope that big company's realize , that they created a mess and without any common sense "write once , run everywhere" will definetly become a thing of past.