Lightweight: Designed for speed, it works everywhere—including vscode.dev—without the bloat. - Source: dev.to / about 2 months ago

It's VSCode, so it's 90% similar to https://vscode.dev. - Source: Hacker News / 3 months ago

It is basically VS Code Web. Try https://vscode.dev/ to see how you feel. If you don't like it you won't like cider. - Source: Hacker News / 3 months ago

GitHub Codespaces provides 60 hours of free compute time every month, which is more than enough for scoped home assignments or interviews. It’s a full VSCode in the browser at github.dev or vscode.dev. - Source: dev.to / 8 months ago

In VSCode extensions this is trivial, this is how you create the 'executable': https://github.com/floooh/vscode-kcide/blob/main/src/wasi.ts ...and this is how you run it: https://github.com/floooh/vscode-kcide/blob/2dfc621aade4a2be06b6a0e703bebb244f5e414c/src/assembler.ts#L33-L40 The asmx.wasm file is a vanilla POSIX cmdline tool (https://github.com/floooh/easmx) which loads and saves files, and the tool has been... - Source: Hacker News / 8 months ago

I look forward to trying this out. It might be a good test-case; this codebase is so convoluted it has actually triggered internal crashes in some analysis tools I've tried on it. For example starting the application under Dr. Memory (https://drmemory.org/) results in a hung process. Source: about 3 years ago

Profiling the game and looking at what time is spent on during the freezes is a start. Checkout https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/event-tracing-for-windows--etw- / https://drmemory.org/. Source: over 3 years ago

Yes, you can use Dr. Memory, works out of the box on windows with mingw and visualcpp. Source: over 3 years ago

Other, heavier, tools exist to the same affect that work cross platform - Dr. Memory being my preference. Source: over 3 years ago

I like to use Dr. Memory - excellent Valgrind alternative for Windows users. Source: about 4 years ago