Re:WebAssembly Interface Types: Interoperate with All the Th...
by coldtea on Thursday August 22, 2019 @03:11AM
(#20765425)
>JVM (Java), Parrot (Perl 6 VM) and CLR (C#) shipped easy, multi-language environments over a decade ago. For some definitions of "easy" and "multi-language".
Java tied a whole ecosystem and was a pain to connect to anything outside, Parrot is a perennially incomplete half-arsed experiment, and C# has been historically tied to the MS ecosystem (and is also a pain to link to from outside).
The promise here is that the new system would have cross platform, cross vendor support (e.g. MS, Apple, Google, Mozilla), and that it wont be a pain to link to from, say, C or Rust or Python.
>WASM won't be able to "solve" these issue any better than the JVM, Parrot, or CLR did.
Doesn't need to. It's enough that it solves the same issue linking to a C library with bindings does, but without re-compilation, with a sandbox, and an easier interface.
I'd like to use e.g. something like Pillow or a numeric lib, etc, in WASM from languages outside Python...
Java tied a whole ecosystem and was a pain to connect to anything outside, Parrot is a perennially incomplete half-arsed experiment, and C# has been historically tied to the MS ecosystem (and is also a pain to link to from outside).
The promise here is that the new system would have cross platform, cross vendor support (e.g. MS, Apple, Google, Mozilla), and that it wont be a pain to link to from, say, C or Rust or Python.
>WASM won't be able to "solve" these issue any better than the JVM, Parrot, or CLR did.
Doesn't need to. It's enough that it solves the same issue linking to a C library with bindings does, but without re-compilation, with a sandbox, and an easier interface.
I'd like to use e.g. something like Pillow or a numeric lib, etc, in WASM from languages outside Python...