6 ms·
This > 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 th
by vineyardmike 3y ago
This
> 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.
- ShroudedNight 3y agoIt seems that NIH also manifests generationally: ? -> CORBA -> RMI -> SOAP -> REST -> GraphQL? ? -> SOA -> Microservices ? -> EDI / X12 -> XML -> JSON p-code -> ? -> JVM -> WASM
- pjmlp 3y agoBefore P-Code there were other ones, there were lots of bytecode based platforms. Burroughs, all Xerox PARC, Lisp Machines, OS/400, Oberon, Limbo, original Modula-2, QuickBasic, Amsterdam Compiler Toolkit, VB, ...
- paulddraper 3y agoOkay, but have you used CORBA? Or EDI? It's like saying we had the Model T, but people just keep inventing new cars.
- ShroudedNight 3y agoI have, albeit not terribly extensively. I will readily agree that there are cogent arguments for replacement that pass the Chesterton's Fence test. But I also see quite a lot of "That's too complicated to bother understanding, I'll just do my own thing"