@zeux@mastodon.gamedev.place
Just stop using it? It was never great.
I actually have a soft spot for VSCode because it allows me to do things like this :)
https://marketplace.visualstudio.com/items?itemName=floooh.vscode-kcide
It's also the only IDE I know which can be configured for WASM debugging, and it feels more lightweight than a "real IDE" like Xcode or Visual Studio.
The latter almost works for JS -> Wasm in Zed; unfortunately while the symbols seem to point to .cpp files, the actual debugging flow shows them referring to .wat files that don't exist, and the debugger doesn't show the C++ source as a consequence. You can still step through, so the debugging engine is clearly working - not sure what's the missing link, never tried this before.
the interesting part of WASM debugging in VSCode is that it both works locally for WASI stuff (running in node.js), but also as remote-debugging for WASM running in the browser. E.g. I can press F5, and the debuggee starts in Chrome while I can step through the (C/C++) code in VSCode. Incredibly useful for WebGL/WebGPU stuff. One needs to glue a couple of plugins together though (see: https://floooh.github.io/2023/11/11/emscripten-ide.html)
@MouseByTheSea @zeux meh, the browser is the last platform where I can simply upload some silly demo without having to justify to some "platform owner" why that silly demo has a right to exist, and users can just click on a link instead of getting all sorts of scare popups how that silly demo will most definitely delete all their data and steal their passwords.
