Hacker News new | ask | show | jobs
by tete 13 days ago
I agree. This is saddening. It seems to often happen in "standard first" scenarios for some reason. I was very happy when CloudABI and POSIX were picked as prior art inspiration.

Now it feels like it moved from "what would we need to get things done and achieve our goals?" to "what could be done and which goals could we achieve?"

Maybe I am missing something, but are the recent changes something that people requested?
1 comments
0x457 13 days ago
Yes, you missed people asking for years: away to do interop between languages in WASM, a way to interact with browser APIs without JavaScript from WASM.

Component model enable both using one thing.

link
garganzol 12 days ago
> way to do interop between languages

This problem stems from the lack of a standardized component model. WASM is merely another casualty of that deficiency - one among hundreds of affected technologies.

The alliance is attempting to solve the problem at the wrong level and only for WASM, rather than addressing the root cause in a way that would benefit everyone.

link
0x457 7 days ago
Why WASM folks need to solve for not WASM?
link
tete 13 days ago
Fair enough. Isn't that another topic more tied to WASM compare to what initially claimed to be a "System Interface" and not a language interface or a browser interface?
link
0x457 7 days ago
Do you know see how components model solves all three?

If WASI decided to keep bespoke runtime capabilities, then you would have whole zoo of:

  - this runtime does support WASI

  - this runtime does NOT support WASI

  - this one supports WASI, but only older spec

  - this claims to support WASI, but X/Y/Z capabilities are bugged
I think WASI switching to components was the right move. Sure, tooling right now maybe meh outside of rust (and even rust is still meh), but once things stabilize good tooling is to follow.
link