I'm not sure I agree with these sentiments... The JS backend gives Nim the potential to attract a whole world of developers, who might not be exposed to the language otherwise. Not that I personally want a bunch of JS devs shaping the future of Nim, but fortunately for us, the language has sensible leadership and decision makers planning its future.
As @gemath pointed out - WASM isn't billed as a replacement to JS, and I'm not sure competitor is even the right word either. I think WASM is the next iteration of binaries in the browser - so think Java Applets, Macromedia Flash, etc... The difference b/w those and WASM is that WASM is an "open standard" and WASM seems to also focus heavily on interoperability b/w JS and Native code compiled to WASM. I think - until someone develops something useful with WASM in another language, or there is real reason to buy into the WASM hype - there's not much reason to sorry about Nim lacking a proper WASM target. You can get there today via emscripten. WASM itself still has a lot of growing up to do anyway, according to - [https://hacks.mozilla.org/2018/10/webassemblys-post-mvp-future](https://hacks.mozilla.org/2018/10/webassemblys-post-mvp-future)/
