I'm one of the folks working with this alliance, and I'm incredibly excited about WebAssembly outside the browser. Happy to answer questions.
Imagine extensions for applications or databases, written in any language you want, with no ability to exfiltrate data. Imagine supporting a safe plugin API that isn't just for C and languages that FFI to C, but works natively with safe datatypes.
> 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://wasmer.io/
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)
2 comments
[ 2.7 ms ] story [ 14.1 ms ] threadImagine extensions for applications or databases, written in any language you want, with no ability to exfiltrate data. Imagine supporting a safe plugin API that isn't just for C and languages that FFI to C, but works natively with safe datatypes.
> 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://wasmer.io/
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)