C/C++ can’t do anything by itself. It needs a compiler, a cpu, memory, and it needs std lib for a platform in order to do basic things like fs access. See, I

C/C++ can’t do anything by itself. It needs a compiler, a cpu, memory, and it needs std lib for a platform in order to do basic things like fs access. See, I can make your statement about anything. Wasm in browser with proper bindings has access to the entire browser stack. Projects like wasmer give wasm a runtime environment absent a browser with a significant amount of capability that grows every day. All without being locked in to any particular language or ecosystem. This is very very powerful. With things like WebGPU down the pipe and the prospect of GPU access directly via wasm, a whole new generation of performant & automatically cross-platform apps is nearly here. I don’t have the resources to maintain countless platform specific codebases. I also cannot afford to have low performance that comes with something like an electron app. But I need the universality of a web app without the lockin to a browser. A wasm target gives me the best of everything. As an example, I converted a ring signature lib to Typescript / js. Then I made a build of it via C to a wasm target and built typescript bindings. The wasm target was between 10 - 100x more performant for this particular implementation. The tooling around wasm doesn’t have a vendor or a code lockin. There is a whole lot more there than “fast javascript” so I would really just suggest keeping an open mind and doing more research. If nothing else, it is another valuable tool to have.