|
|
|
|
|
by ifwinterco
333 days ago
|
|
The entire DOM API is very coupled to JS, it's all designed with JS in mind, any new and future proposed changes are thought about solely through the lens of JS. If they introduced a WASM API it would perpetually be a few months/years behind the JS one, any new features would have to be implemented in both etc. I can see why it's not happened (edit) And yes, I think the intention of WASM was either heavy processing, or UI elements more along the lines of what used to be done with Java applets etc. potentially using canvas and bypassing the DOM entirely, not as an alternative to JS for doing `document.createElement` |
|
Is it though? I thought it was all specified in WebIDL and all the browser vendors generate C++ headers from it too.