I have almost no exposure to JS but what I have seen so far in WASM projects didn't seem to require that much of a non-usual work but, of course, YMMV. To me t

I have almost no exposure to JS but what I have seen so far in WASM projects didn't seem to require that much of a non-usual work but, of course, YMMV. To me the most challenging part seemed to be in the domain of debugging when things would go south because all of the sudden you have to become very intimate with how things work under the hood and across the whole stack: JS -> V8 -> WASM runtime -> Emscripten -> C++. There's not many people capable of doing that job. > user experience feels un-browser-like Perhaps Photoshop is not the classical example but I think it's one of the most craziest ones out there - humongous and extremely complicated C++ codebase consisting of every imaginable optimization and heavy lifting deployed as a WASM "plugin". [1] https://medium.com/@addyosmani/photoshop-is-now-on-the-web-38d70954365a https://medium.com/@addyosmani/photoshop-is-now-on-the-web-3... [2] https://web.dev/articles/ps-on-the-web https://web.dev/articles/ps-on-the-web