I don't think allowing scripting of the DOM was a great idea personally. The goal of the original web was layout and structure of information and the links between them.
Javascript bulldozes over both the DOM and URL's.
The nice thing about web assembly from what I've read, is that it doesn't allow access to the DOM. It basically creates its own sandbox that is then included on the page.
You can INCLUDE interactivity in the page, but, you can't overwrite the page itself.
Because of this it kind of encourages a progressive web design style. You will design the html/xml first then you will wrap the interactivity within.
This will encourage a separation of concerns between highly interactive, more complicated code, and layout and structuring of documents.
There will be some issues to be overcome and I doubt it will be as ideallyic as I imagine, but I think overall it would be a more sane web being able to select 'disable javascript' without any worries.
Javascript bulldozes over both the DOM and URL's.
The nice thing about web assembly from what I've read, is that it doesn't allow access to the DOM. It basically creates its own sandbox that is then included on the page.
You can INCLUDE interactivity in the page, but, you can't overwrite the page itself.
Because of this it kind of encourages a progressive web design style. You will design the html/xml first then you will wrap the interactivity within.
This will encourage a separation of concerns between highly interactive, more complicated code, and layout and structuring of documents.
There will be some issues to be overcome and I doubt it will be as ideallyic as I imagine, but I think overall it would be a more sane web being able to select 'disable javascript' without any worries.
Just my 2 cents.