5 ms·

First of all, congrats on forming the alliance! > Imagine extensions for applications or databases, written in any language you want, with no ability to exfilt

First of all, congrats on forming the alliance! > Imagine extensions for applications or databases, written in any language you want, with no ability to exfiltrate data That's what we are working towards on Wasmer, the server side WebAssembly runtime - https://github.com/wasmerio/wasmer https://github.com/wasmerio/wasmer In fact, we already have a lot of different language integrations (maintained by us and the community) and our software is the pioneer on the space. Is there any reason on why you think is a good idea to do a side-alliance instead of collaborating with us and the community so users and developers can be the ultimate beneficiaries? (it's good, it just seems is not an alliance made for the users, which it's a bit weird from my perspective)

npmccallum 7y ago
Disclaimer: I'm from the Enarx project (https://enarx.io https://enarx.io) which is associated with the BytecodeAlliance. I think a good analogy is: wasmer is to qemu as BytecodeAlliance is to rust-vmm. Wasmer is a general purpose WASM runtime. But BytecodeAlliance is a place to build tooling for the construction of runtimes (WASM or otherwise), including special purpose runtimes. I think there is a lot of space for both in the growing non-browser WASM market.
- syrusakbary 7y ago
  Agreed! (regarding the non-browser WASM market) Not sure if I got the analogy, but all I can say is that I'm very excited about the Enarx initiative :)
- jedisct1 7y ago
  How does Enarx differ from MesaTEE?
baybal2 7y ago
> First of all, congrats on forming the alliance! No Google on board, it means no Chrome support
- amaranth 7y ago
  What does Chrome have to do with a plugin for my image editor or a command line tool on my server?
  - coldtea 7y ago
    Obviously it has with it controls the biggest OTHER use case for WebAssembly (the v8 runtime used in both the browser and Node) and thus can very much influence WebAssembly towards what they like (or slow it down adoption wise etc), even in areas not related with the web directly...

npmccallum 7y ago

Disclaimer: I'm from the Enarx project (https://enarx.io https://enarx.io) which is associated with the BytecodeAlliance. I think a good analogy is: wasmer is to qemu as BytecodeAlliance is to rust-vmm. Wasmer is a general purpose WASM runtime. But BytecodeAlliance is a place to build tooling for the construction of runtimes (WASM or otherwise), including special purpose runtimes. I think there is a lot of space for both in the growing non-browser WASM market.

syrusakbary 7y ago
Agreed! (regarding the non-browser WASM market) Not sure if I got the analogy, but all I can say is that I'm very excited about the Enarx initiative :)
jedisct1 7y ago
How does Enarx differ from MesaTEE?

baybal2 7y ago

> First of all, congrats on forming the alliance! No Google on board, it means no Chrome support

amaranth 7y ago
What does Chrome have to do with a plugin for my image editor or a command line tool on my server?
- coldtea 7y ago
  Obviously it has with it controls the biggest OTHER use case for WebAssembly (the v8 runtime used in both the browser and Node) and thus can very much influence WebAssembly towards what they like (or slow it down adoption wise etc), even in areas not related with the web directly...