News for hackers. Stuff that matters.
Re:VSCode-WASM: Implement a first version of a WebShell by nl on Monday May 01, 2023 @01:00AM (#35769253)
> allows developers to use WASI easily when creating new extensions

What is WASI?

Re:VSCode-WASM: Implement a first version of a WebShell by re-thc on Monday May 01, 2023 @01:18AM (#35769342)
API for Webassembly. Common interface.
Re:VSCode-WASM: Implement a first version of a WebShell by nindalf on Monday May 01, 2023 @01:48AM (#35769460)
> WASI stands for WebAssembly System Interface. It's an API designed by the Wasmtime project that provides access to several operating-system-like features, including files and filesystems, Berkeley sockets, clocks, and random numbers, that we'll be proposing for standardization.

Read more here - https://github.com/bytecodealliance/wasmtime/blob/main/docs/...

Re:VSCode-WASM: Implement a first version of a WebShell by throwaway525142 on Monday May 01, 2023 @05:08AM (#35770542)
Re:VSCode-WASM: Implement a first version of a WebShell by cjbprime on Monday May 01, 2023 @01:50AM (#35769471)
Am not expert, but here's the understanding I've picked up:

When you use JavaScript through Node, your JS gets the ability to open files and make network sockets and so on, because there are a set of APIs implemented by Node and exposed to your JS code, like so:

JS <-> native APIs <-> Node implementation of platform-specific operations

WASI applies to WebAssembly instead of JS. So again if we're on Node:

wasm <-> native APIs (WASI) <-> Node implementation of platform-specific operations

But WASI is much more general than Node's APIs, and meant to be used by different engines in different environments (browsers, native bindings, etc).

Re:VSCode-WASM: Implement a first version of a WebShell by tcper on Monday May 01, 2023 @08:16AM (#35771742)
Simplely, it's wasm's POSIX