> it becomes usable [...] for interfacing with the web browser
As soon as you add DOM integration... all the things people hate about JS in terms of architecture and compromises will show up in WASM.
As soon as you add DOM integration... all the things people hate about JS in terms of architecture and compromises will show up in WASM.
You hate objects... basically?
This has likely changed since I last used javascript, but in the bad old days, if you wanted to specify a "type" (in the structural sense- a common set of fields that you might construct instances of), you build that type with statements rather than declarations. That feels icky. Also, that means that any potential IDE has to interpret your code (rather than simply parsing declarations) to provide any real support for you, which meant it took forever for IDEs to provide things like autocomplete (let alone foolproof renaming).
You declaratively specific the "class" (it's just an Object under the hood, it's mostly sugar for prototypes) and then you could just to instanceOf to test if it's your "type".
I mean in JS basically everything is an object so if you're constructing a "type" you're constructing an object no matter what.
Because it does basically everything else (or is spec'd to).