3 ms·

Why does it have the chance to be superior?

by lifty 3y ago

samsquire 3y ago
Compiling native application to operating systems that Wasmer is compiled for including the browser and have the code seamlessly work in all of them, I think that's really promising. JVM forces you to write in Java or a JVM targeted language but WASM lets you compile any language that creates a WASM backend.
- 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 ago
    It seems that NIH also manifests generationally: ? -> CORBA -> RMI -> SOAP -> REST -> GraphQL? ? -> SOA -> Microservices ? -> EDI / X12 -> XML -> JSON p-code -> ? -> JVM -> WASM
    - pjmlp 3y ago
      Before 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 ago
      Okay, 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 ago
        I 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"
- laxd 3y ago
  > Compiling native application to operating systems that Wasmer is compiled for including the browser and have the code seamlessly work in all of them. 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 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.

Why does it have the chance to be superior?

by lifty 3y ago

Why does it have the chance to be superior?

Compiling native application to operating systems that Wasmer is compiled for including the browser and have the code seamlessly work in all of them, I think that's really promising. JVM forces you to write in Java or a JVM targeted language but WASM lets you compile any language that creates a WASM backend.

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 ago
  It seems that NIH also manifests generationally: ? -> CORBA -> RMI -> SOAP -> REST -> GraphQL? ? -> SOA -> Microservices ? -> EDI / X12 -> XML -> JSON p-code -> ? -> JVM -> WASM
  - pjmlp 3y ago
    Before 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 ago
    Okay, 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 ago
      I 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"
laxd 3y ago
> Compiling native application to operating systems that Wasmer is compiled for including the browser and have the code seamlessly work in all of them. 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 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.