4 ms·
No need to recompile means you can run the same, guaranteed known, signed, etc code everywhere. Purpose-built sandboxing means you can run untrusted code more
by nine_k 6y ago
No need to recompile means you can run the same, guaranteed known, signed, etc code everywhere.
Purpose-built sandboxing means you can run untrusted code more safely — e.g. at the network edge, like a Cloudflare worker, a lambda, etc. Same for third-party plugins in apps, etc.
An open standard and open implementations gives you some assurance against lock-in, licensing changes, patent suits, etc.
- kaba0 6y agoAll of it already exists with the JVM.
- jillesvangurp 6y agoThe JVM is rather heavy weight and typically slow to start even when you do have enough resources to run it. That rules out edge computing. Graal AOT compilation is more similar but not a general purpose thing currently as it only works with tools and languages optimized for that. I say this as a Kotlin/Java developer. I know and love the jvm but it's just not a lightweight option suitable for edge computing or serverless computing (it works but the jvm startup overhead + binary size is annoying).
- pjmlp 6y agoJava has had AOT compilation support since around 2000, when commercial JDK vendors started supporting it, what it lacked was free beer AOT compilation, as GJC never really did it without issues and was quickly abandoned when OpenJDK came into the scene.
- flohofwoe 6y agoIsn't the JVM too high level for compiled languages without garbage collection? E.g. can I efficiently compile C to the JVM without asm.js-style hacks which degrade performance?
- kaba0 6y agoIt may be. As far as I know GraalVM can compile it AOT, but I don’t know about it’s performance characteristics.