Looking at James Gosling's Twitter, I think there are many SEs who feel that they have already estimated the JDK migration plan, or that they need to be fixed. This is not a dream, but an urgent and important news that must be considered in reality.
Actually, I was [investigating] about the JDK (https://qiita.com/arimas/items/7bbba7dbf7e8068da79c), but this is the second important force to bring to the introduction.
Since it is a story that I need to know, including re-estimation, I made a quick comment and considered it as an important comment. However, I can't introduce much because there was only news including WolrdWide so far, but I hope it helps. (I'm sorry if the translation is wrong)
https://aws.amazon.com/jp/blogs/opensource/amazon-corretto-no-cost-distribution-openjdk-long-term-support/
Amazon has a long and deep history with Java. I'm thrilled to see the work of our internal mission-critical Java team being made available to the rest of the world" — James Gosling
Amazon has a deep and long relationship with Java. We are thrilled that the work created by our Java team will be widely used-James Gosling
In case any upstreaming efforts for such patches is not successful, delayed, or not appropriate for OpenJDK project, we will provide them to our customers for as long as they add value.
Even if (Amazon Correto) doesn't provide a patch, is delayed, or isn't appropriate for an OpenJDK project, we'll provide it if it's worth it to our customers.
We're making these available to customers with no-cost, long-term support, with quarterly updates including bug fixes and security patches. AWS will also provide urgent fixes to customers outside of the quarterly schedule
We plan to offer zero-cost, LTS, quarterly bug fixes, and security patches to customers (using critical systems). And in case of emergency, we will provide other than that.
Amazon may have come up with a JDK remedy that would cause us to stop thinking, "This is all you need." If you receive it at face value. However, as mentioned in the above comment, it is expected that there will be a divergence * from the Original OpenJDK, so it will be difficult if you want to switch to another JDK later. A design that can be replaced is required.
It is not as easy as switching from Docomo to Softbank, so please be careful about the special notes of the quote. JDK from Java 11 During the Warring States period, Java engineers were forced to consider design when using OpenJDK.