Gartner might know licensing but it doesn't look like they know much about Java.
> If they moved applications to Java 17, they could avoid the change, but it would involve significant work and, for many, would not be viable.
Which Java 17? Oracle Java 17? That won't avoid the licensing requirements.
> Similarly, the option to upgrade all Java applications to the latest release of OpenJDK is most likely off limits, owing to the work involved.
Er, what?
> In the viable-but-hard-work category come the options of switching to third-party Java products
How is "moving to a third-party Java product" easy but "moving to the latest release of OpenJDK" hard? This is nonsense
Switching to Azul or any of the other listed "third part Java product" is, if anything, more complicated than switching to OpenJDK, which involves no licensing checks. And switching to OpenJDK doesn't mean also upgrading to Java 17 - OpenJDK 8 and OpenJDK 11 are available for download. I'm actually starting to view Oracle's change as a good thing - if it can wean some of our, er, more conservative customers off Java 5 through 7 and onto OpenJDK 8.