Sure, but you can get frameworks that generate that for you. I’ve written whole webpages in WASM without writing any JS.
You don’t get around reading JS documentation, though. Especially the DOM API is just documented as JS, and you basically hope that your framework makes it obvious enough how to write that in your non-JS language of choice.
The == operator in JS will try to cast the things being compared and do all kinds of ‘smart’ assumptions about what equality means. This is why everyone uses === instead…
No, they’re discussing the way forward and what they think makes sense. In fact, they’re even clearly stating that there will be pain, because Wayland intentionally does less than X11. And they’re encouraging people with unsolved pain points to speak up.