Until there are other companies actually implementing JEPs into OpenJDK in the same volume as Oracle, OpenJDK == Oracle.
This is a now somewhat outdated report of contributions per company to OpenJDK.
https://blogs.oracle.com/java-platform-group/building-jdk-11...
But they didn't. And have in fact continued to invest in the ecosystem e.g. GraalVM, OpenJDK.
'Poisoning' is taking full control and monetizing everything, making everything closed source.
GraalVM is in their eyes, going to be a money-making investment. The only extent to which it might be partly OSS is a function of how much they really had to give away.
Oracle's objective with Java is to take a huge bite out of the Enterprise and do with Java what they did with their DB.
Imagine if we all needed to talk to an Oracle sales person to make our app :)
I invested several years at coming up to speed with Java 8+ (using templates, rx, streams, the new time APIs). It was not hard, but difficult to unlearn some C++ idioms around templates, consts, reference model and object lifecycle management.
Clearly this driven by Oracle's continuous poisoning of Java ecosystem (eg https://headcrashing.wordpress.com/2019/05/03/negotiations-f... )
And I think Kotlin is a solid step forward from the Java without the baggage of pre JDK 1.7 idioms.
But for a small (often single dev) shops trying to compete in Android marketspace, it is quite hard to maintain this rate of change (plus incorporating all the new (and better ways) of doing android with androidx )