News for hackers. Stuff that matters.
Re:WASI 0.2.0 and Why It Matters by flohofwoe on Friday January 26, 2024 @11:27AM (#39144451)
Might be part of the nerd kingdom for you, but I recently made pretty cool use of WASM+WASI in a VSCode extension:

https://floooh.github.io/2023/12/31/vscode-wasm-wasi.html

Also quite a few 'CPU nerds' found my 'visual6502 remixes' useful so far:

https://floooh.github.io/visual6502remix/

https://floooh.github.io/visualz80remix/

Development experience with Emscripten and WASI SDK is fine really (in the sense that these are "just another gcc-style cross-compilation toolchain"), and with those it's not much different than bringing a C code base to any other platform. It depends a lot on how portable the code is in the first place of course.

Re:WASI 0.2.0 and Why It Matters by boomskats on Friday January 26, 2024 @01:42PM (#39146265)
I read your post on WASM debugging with Emscripten and VSCode[0] just last week, thought it was amazing!

Not quite the same, but tangentially related since we're talking WASM+WASI and VSCode extensions - I have high hopes for the vscode-wasm[1] project. The VSCode extension host is a massive hog, and this seems like a big step in the right direction.

[0]: https://floooh.github.io/2023/11/11/emscripten-ide.html [0]: https://github.com/microsoft/vscode-wasm

Re:WASI 0.2.0 and Why It Matters by flohofwoe on Friday January 26, 2024 @05:21PM (#39149486)
Yeah, this vscode-wasm thingie is exactly what I'm using to run a command line assembler tool in VSCode. Pretty neat, only downside currently is that it is only available as pre-release, which makes installing extension which depend on vscode-wasm awkward for the user.