> Oracle broke compatibility between Java 8 and Java 9+,
No it didn't. Introduction of modules (Java Platform Module System (JPMS)) would be mostly transparent to majority of users.
> so many of the libraries that have a dependency on older functionality are not getting maintained.
Any example? (I already herad the same argument on bluesky and asked for example and suprisingly didn't get it either)
The biggest issue around that time was switching from javax to jakarta namespace but that's somewhat on the side of the Java versioning.
> Java 8 is turning into a dangerous space because even though the JDK is getting patched quarterly, much of the components that work with it are not.
Again - examples?
If the library is not update then it could happen in any ecosystem - python, c# and whatnot.
> It is only going to get worse. SpringBoot, for example, requires either a commercial contract for Java 8/11 support or Java 17+ for the community supported stuff.
Of for f sake - if you are still stuck on Java 8 (released a decated ago) and didn't update then it's only your fault. Supporting ancient platform cost money so you either put that money to be up to date or you pay companies to maintain compatibility you ancient stock. MS is doing the same with old OSs and virtually any other company requires to pay/pay more to support old stuff... (because it costs money)