Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Also most of them are also only support programming in Java. This always limited running arbitrary C code, or other languages like C++, Go, Nim, Rust, etc.


The JVM is Turing complete. So you can run any language you please on it.

The question is—as always—how efficient this is.

But this goes also the other way around.

Even you can in theory run arbitrary languages on a WASM runtime the question how efficient this is stands also!

And in fact running anything else than "C languages" in WASM is at least as inefficient as running "C languages" on the JVM…


> And in fact running anything else than "C languages" in WASM is at least as inefficient as running "C languages" on the JVM…

Hell, it is a really safe bet to say that running a C-like program on the JVM is much much faster than porting a whole runtime (which is very performance-oriented) on top of a runtime and make it run some code. Wasm simply can’t expose the optimizations runtimes routinely make use of (template interpreters for example))




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: