3 ms·
It's great to see more use cases of Wasmer [1] out there. I'm excited for what's coming next on this front :) [1] https://wasmer.io/ https://wasmer.io/
by syrusakbary 3y ago
It's great to see more use cases of Wasmer [1] out there. I'm excited for what's coming next on this front :)
[1] https://wasmer.io/ https://wasmer.io/
- laerus 3y agowhat's coming next is replacing wasmer with wasmtime [1], the runtime closely following wasm and implemented by the same people designing the standard itself. [1] https://wasmtime.dev/ https://wasmtime.dev/
- syrusakbary 3y agoWhile that's not true, since the Wasm spec is designed mainly by the browsers, I appreciate the hustle-trolling haha In any case I wonder what's the need for try to push Wasmer down. Here are your previous comments, all hateful against Wasmer on different announcements: 1. https://news.ycombinator.com/item?id=36128284 https://news.ycombinator.com/item?id=36128284 (on WASIX launch) 2. https://news.ycombinator.com/item?id=33835683 https://news.ycombinator.com/item?id=33835683 (on WAI bindings) Honest question: are you related to the Bytecode Alliance at all? (I saw a comment from you in HN promoting a company from that alliance)