realistically, would you care at all if node.js dropped wasi support in core
-
-
Replying to @cjihrig
I think Node can currently get away with not supporting it without feeling many downsides. Similar to how Node has been able to get away with not supporting WebSockets for a long time. 1/2
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts @cjihrig
But WASI is going to succeed, even without Node's adoption. Too many groups have a stake in its success. I think it would be beneficial for Node to support WASI in core so it can implement and influence the spec. ES Modules showed how hard it can be to integrate after the fact.
1 reply 0 retweets 3 likes -
Replying to @yoshuawuyts
i'm not disagreeing with any of your points but: 1. node gets most of its wasm from V8 2. node isn't a likely compile to wasm target 3. there already isn't anyone influencing the spec, and the team feels like a bit of an inner circle to be perfectly honest
2 replies 0 retweets 1 like -
Replying to @cjihrig
A hypothetical that doesn't seem entirely unlikely: ServiceWorkers get a WASI definition which turns into the canonical definition of what HTTP servers should look like. Node might want to have a say in that. It's big enough that it could at least try and be part of convos.
1 reply 0 retweets 1 like -
Replying to @yoshuawuyts @cjihrig
I think folks are right to point out that it has a lot of potential to replace native bindings. It seems attractive for e.g. DB vendors to replace their various language-specific clients with a shared core targeting WASI. Node being an convenient target seems beneficial.
2 replies 0 retweets 0 likes -
Replying to @yoshuawuyts @cjihrig
Oh also less in the hypotheticals: this also all applies to my work. I don't have much interest in writing Node code directly anymore. But would love to e.g. be able to run the Rust HTTP framework I've built on Node's stack. Or enable some of my Rust libs to be used from Node.
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
out of curiosity, and for my own knowledge, what is the advantage to running your code as wasm in node vs. running in a dedicated wasm runtime?
1 reply 0 retweets 0 likes
Applications vs libraries. A dedicated runtime is for apps; running in Node is for libs. Another common example I see is SDKs: write an HTTP client once, and share between multiple langs. If WASI support in core, then there's a chance to e.g. make hooks support really good.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.