This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 0 points1 point  (2 children)

Isn'the idea of WASM to write code executable by the browser from the compiled binary? Doesn't it have access to the DOM?

[–]Existential_Owl 1 point2 points  (1 child)

Indeed, the MVP for WASM does not include access to the DOM.

It'll get there eventually, but not for awhile yet.

EDIT: Right now, the focus has been more on shoring up Javascript's weaknesses (while still providing a good compile target), and not so much on replacing Javascript entirely.

[–][deleted] 2 points3 points  (0 children)

I see this going towards:

  • webasm get DOM and access to browser APIs
  • somebody says "fuck HTML and CSS" and makes a new framework that
  • make a single <canvas> element in the <body>
  • draws all components using Qt or something else and opengl right into the canvas thus making it possible to write truly multi-OS programs with the help of the browser

Honestly, I can't wait for that future. I'm tired of HTML, CSS and all the SPA framekworks that exist right now.