I don’t feel that there are nay-sayers. It is just a different use case than the core team envisions. If some people have the skills to put together a JS transpiler, then I am sure the core team would rather get that energy focused on the main compiler work. I would probably feel the same.
Also I suspect people have not tried out isomorphic coding (like we do with https://hyperstack.org and ruby) and until you see it in action it is a “too good to be true story”.
Regarding WASM… the Opal transpiler goes to JS, and so that is a known and working use case. I would worry about these issues with WASM:
- debugging
- interoperating with JS code
- interoperating with the DOM
All these are fixable, but I think it would add a lot of work. Sure with WASM you could probably get up and running quicker, but you would be on a desert island until the above issues were solved.
Going to JS immediately fixes these issues.
If you have not played with https://hyperstack.org you should, and you will see what I mean.
I could be wrong about all of the above, but that is where I am coming from.
Cheers!