> a fully-featured JS replacement, targetable in any language
Any language can target a combination of JS and Wasm, right now, to get a "fully-featured JS replacement". How would adding more features to Wasm improve that situation?
How does substituting JS for some other JS achieve a goal of replacing JS? If someone wanted to replace C, would you suggest C as a C replacement? That's nonsensical in context.
Adding browser interop to Wasm that obviated the need for JS would, obviously, achieve that goal. Hence the improvement.
How does substituting JS for some other JS achieve a goal of replacing JS? If someone wanted to replace C, would you suggest C as a C replacement? That's nonsensical in context.
Adding browser interop to Wasm that obviated the need for JS would, obviously, achieve that goal. Hence the improvement.