[sunkencity]

Sure it takes a while to load and there's bloat, but the bloat is everywhere now.

On the bad site of the JVM and assorted Java tools is that they are second class citizens of the unix world. The command arguments are all messed up, much like a windows tool ported to unix, and the interaction with the rest of the unix stack like sockets, files are all solipsistic and off, which leaves an ill stink on everything touched by it.

One of the things I find funny with java is the once upon a time much touted security model, fast forward a couple of years and the event of android - using the unix security model and none of the java stuff.

[stcredzero]

Sure it takes a while to load and there's bloat, but the bloat is everywhere now.

This is exactly the kind of development culture that produces heavyweight, unresponsive tools.

[pjmlp]

Well, except for the type safety of Java, only allow native code to be compiled to shared objects for implementing Java native methods and exposing all OS APIs outside what is required for graphics and real time audio via JNI.

If it wasn't for the pressure of game developers, the NDK wouldn't even exist.

Remember Brillo? It was supposed to be like Android, but using C++ frameworks instead, as presented at Linux Embedded 2015 conference.

Guess what, when it got recently re-branded as Android Things, it switched to the Java Frameworks instead and it doesn't even allow for the NDK, with the user space device drivers being written in Java.