AssemblyScript Drops Support for WASI

In the comments, they reply with a link to a longer form writeup on why. I think it's very valid a claim here, that WASI is reinvention & redefiniton, a parallel universe, to the amazing work that's happened in web standards (ex: new WinterCG).

https://www.assemblyscript.org/standards-objections.html

It would be excellent to see WASI folks refocus on working more with the web, as opposed to building their own parallel system that uses none of the existing common genetic material that comprises the web. (That said, efforts like FileSystemAccess have been a pretty lurching slow progress, & certainly really good material like capability systems are fairly absent in this smaller spec).

I have to agree, I think their is a real danger. That said, there's also a lot of drama, and I remember other incidents like UTF16 that similarly got blown out of proportion, werent kept at a reasonable level.

> A new week, a new major AssemblyScript version! Among general improvements, we have removed support for WASI and from now on consider WASI, derived proposals, the W3C's endorsement of its subgroup and the Bytecode Alliance's practices harmful to open Web standards.

This post is a dupe:

https://news.ycombinator.com/item?id=32562230 (8 comments - 15 days ago)