Another good write-up which gives more context to this release, and it touches on POSIX in relation to the component model.

https://blog.sunfishcode.online/wasi-preview2/

This does such a good job laying out the real fundamentals of what's happening. Capabilities model, component-model; it's well covered and nicely tied together.

The WasmCom keynote What is a component? (and why?) by Luke Wagner is also a great intro. https://youtu.be/tAACYA1Mwv4

If you are looking for one video in this thread to watch this is it. ^

Luke crushed it.

I saw him give this talk at a work event and I fully agree, it's incredibly informative and he presents the material in an engaging way!

Thanks for sharing. I often wondered why we didn’t just create a subset of POSIX for the web and wasm, this seems to answer my questions.

Other team ask themselves that question and created WASIX. I'm looking into it.

Because to me it seems only logical, to have POSIX that can work on the web.

This is about WASI and WASI is outside the web browser.

WASI Co-chair here: WASI is for the Web as well as beyond. The jco project (https://github.com/BytecodeAlliance/jco) provides an implementation of the Component Model and WASI Preview 2 for JavaScript systems. Right now, node.js support is complete, but support for Web embeddings is in progress and coming soon.

Why waste time figuring out I need five Franks and 10 Amys? I'll just dial up a one of me and head home early.

Maybe the future is everyone working on their own AI worker and licensing it out to companies to deploy in the cloud.

This is what the author was wondering at the end of the article. The discovery blurs the line between the two. There is now the question if they may be the same thing.

just add it yourself. <grin>