Yes I understand what you mean, but in some ways the JVM needs big improvements. The first one that comes to mind is getting rid of the garbage collector because it causes so many difficult problems in terms of predictability. One of the reasons I love Swift so much is that it manages to do away with such a construct.
Also the JVM is (still) full of stuff that doesn't make that much sense in a microkernel environment, especially for running micro-services. But at least with Jigsaw it becomes possible to make it lighter. The overall memory consumption of JVMs is also a concern. Anyway, realistically, what can we achieve today? JVMs like the OpenJDK one still need a lot of OS-level services to operate, and in the short term it will be difficult to do without. Regards, Serge... On Wed, Feb 13, 2019 at 2:56 PM Ranx <r...@enjekt.org> wrote: > > Serge, > > Sure. Absolutely. What I meant is that part of the problem that Loom is > solving is that of system thread context switching from user to kerenel mode > and back. > > Running the JVM in kernel mode in an unikernel eliminates that context > switch without the need for an extra construct. > > But that's really an aside for me, it's the ability to run the JVM directly > on the hypervisor with only a slim OS between the two that appeals to me. > > > > > -- > Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
