> JVM forces you to write in Java or a JVM targeted language
And this
> WASM lets you compile any language that creates a WASM backend
Are basically the same thing.
There’s no fundamental reason that all these languages couldn’t target JVM byte code instead of WASM. It never happened, not nearly as much as WASM backends are, but it could’ve.
? -> CORBA -> RMI -> SOAP -> REST -> GraphQL?
? -> SOA -> Microservices
? -> EDI / X12 -> XML -> JSON
p-code -> ? -> JVM -> WASM
Burroughs, all Xerox PARC, Lisp Machines, OS/400, Oberon, Limbo, original Modula-2, QuickBasic, Amsterdam Compiler Toolkit, VB, ...
Or EDI?
It's like saying we had the Model T, but people just keep inventing new cars.
And thanks to stuff like this, contemporary browsers are now so complicated that they only run on the top handful of platforms. So how is it progress? I bet JVM still runs more places than modern browsers.
> VM forces you to write in Java or a JVM targeted language but WASM lets you compile any language that creates a WASM backend.
WASM forces you to write in something that has a WASM backend just like JVM forces you to write in something that has a JVM backend. It's just the same all over again. And again.
JVM forces you to write in Java or a JVM targeted language but WASM lets you compile any language that creates a WASM backend.