4 ms·
Nah. The JVM must go; we have Docker and the universal platform are Linux ELF binaries so the entire "bytecode" concept makes sense for the compiler (i.e. LLVM)
by pojntfx 6y ago
Nah. The JVM must go; we have Docker and the universal platform are Linux ELF binaries so the entire "bytecode" concept makes sense for the compiler (i.e. LLVM), but no longer at runtime. It's just bloat.
- cageface 6y agoKotlin native might eventually make the JVM superfluous but for now there are a lot of benefits to being on the JVM including great performance, a huge ecosystem of Java libraries, and very battle hardened monitoring and debugging tools.
- hocuspocus 6y ago> Kotlin native might eventually make the JVM superfluous That is probably never going to happen. GraalVM native images are a more realistic approach in this space, and even that is not trivial in most cases.
- lmm 6y agoThe JVM does what Docker does for far less overhead and is easier to understand and upgrade.
- erik_seaberg 6y agoBytecode is simple enough to alter at load time. This gives you aspect-oriented programming and instrumentation of everything that statically linked binaries have never offered. And I don't think anything compares to the JVM's GC throughout yet; why roll your own if it's slow?