Well all this has been true for 10 years. There is still a little life in Java desktop GUIs because all the Java IDEs are written in Java (Netbeans and IntelliJ

Well all this has been true for 10 years. There is still a little life in Java desktop GUIs because all the Java IDEs are written in Java (Netbeans and IntelliJ on Swing and Eclipse on SWT), but no one wants line-of-business software that is thick client, and they haven't since they realized they could reduce administration costs, and lose little functionality. (The exception in my experience being JPL which does some SWT work). The two interesting things that actually compete with Java (JVM) would be LLVM and WebAssembly (or asm.js if you prefer). On another front there is the thing that is competing with a big chunk of the SmallTalk OOP GUIs, a little thing called React. And actually Redux (or something like it) may turn out to be even more influential. My take is that the functional dynamic DOM environment of the browser complete with run-time remote linking and compiling is like the harsh environment of Arrakis, which was the only thing that could have given rise to such hardy technology. P.S. I really have to wonder how much a combination of `System.out.println` and `public static void main(String[] args)` cost the Java ecosystem. Not to mention the Date and File 'idioms'. Having nice collections and solid vm spec and implementation doesn't mean you get to ignore API usability. Sigh.