No mention of anything mobile even though there are a few billion phones out there running Android with a huge app ecosystem of Java and Kotlin based stuff. Of course, that's a non Oracle flavor of Java as Sun sort of lost the plot on the J2ME front (another omission). J2ME was of course more successful than applets ever were until Android happened.
Listing Eclipse and Netbeans (1 bullet) before Intellij (arguably more popular than those two combined) is also a bit weird. In any case, Intellij has largely switched to Kotlin, which is of course a language Jetbrains, the creator of that IDE helped create to replace Java. So nice that they still get a mention. But really, that whole ecosystem is now powered by Kotlin more than Java.
Spring/Spring-boot is another painful one for Oracle because it largely sidelined J2EE related products and standardization. Tomcat and Jetty sort of survive as low level components you can optionally use to run that. The Spring ecosystem is shifting to Kotlin rapidly as well. As is Android, of course.
So, it's understandable why Oracle prefers to not talk about those because these are all examples of where Java was successful but Oracle/Sun wasn't.
I'm thankful for J2EE and things like EJB 2. It's complexity gave rise to Spring and it's amazing ecosystem of frameworks and tooling that we have today.
However, as soon as they rolled JavaFX into the JDK I knew it would be a nightmare for me. Without author status in JBS you're relegated to being a second class citizen who has to submit bugs though the poor door (bugs.java.com) and JavaFX fixes couldn't be pushed out as quickly because of being tied to the JDK.
That was after years of broken promises about mobile which didn't help. They were also claiming to make massive investments in JavaFX, but if you HG churned the repo there were only a few developers doing all the work.
It's too bad because I really liked JavaFX. It was nice to develop with and I'm convinced that Oracle's mismanagement is the primary reason it wasn't more successful.
I completely gave up on JavaFX the day Microsoft bought Xamarin. My impression at the time was that Oracle just didn't care about JavaFX and barely supported their own developers. AFAIK they never did anything to encourage 3rd party developers even though there was some really cool stuff. Ex: Microsoft ended up owning RoboVM.
I also remember being frustrated the first time I looked at the JavaFX repo myself and saw how few committers there were. All the while Oracle would be simultaneously claiming they're investing in the tech, but actually dumping stuff [2] on the community. It's like they viewed open source as nothing more than a way to externalize costs for things they didn't want to maintain.
I never had the inside track on anything, so I don't know what the real story is, but my impression of it has always been that it was badly managed by someone higher up the chain than the people that managed JavaFX directly. Based on my experience everyone on the JavaFX team always made a ton of effort and tried foster a small but growing community.
Speaking of community, it was plagued with the same kind of doublespeak. Oracle would be on the mailing list telling everyone they wanted to work with the community [3] at the exact same time they were telling all of us to file our bugs using a plain text input box on bugs.java.com. How the hell do you submit a runnable test case using a single, 4 line high text box?
And if you need any kind of indicator to demonstrate Oracle's lack of ability to foster a developer community or provide developers with modern resources, go look at that bug filing system I keep complaining about. It's still the same awful system that looks like a holdover from the 90s.
This is all just my opinion, but I honestly believe Oracle squandered a huge opportunity with JavaFX.
1) https://bugs.openjdk.java.net/browse/JDK-8091544
2) http://mail.openjdk.java.net/pipermail/openjfx-dev/2015-Janu...
3) http://mail.openjdk.java.net/pipermail/openjfx-dev/2015-Dece...