Hacker News Reader

I know this question has been asked a million times, but will WebAssembly ever get native DOM access? Seems like that would be a good catalyst for switching away from JavaScript, at least on the client side.

View on HN

Do you need native access? Frameworks like Blazor are doing some interesting stuff without it. Sure there's still a translation layer and JavaScript code in between but overall the project is starting too look really interesting as far as alternatives to JS go.

Of course it could be another Silverlight in the making.

Blazor computes the DOM deltas in webassembly/.NET code in the browser and then sends those deltas to the translation layer which then performs the changes to the DOM. This process would get a considerable performance boost if webassembly were allowed to access the DOM directly.

Silverlight required a plug-in. That's a barrier to adoption that they never overcame. When plugins were outlawed it was impossible to continue Silverlight. Microsoft had seen the writing on the wall and had effectively abandoned Silverligt as a strategic product long before that. Blazor Webassembly is not in the same situation. Webassembly is not going to be pulled. Webassembly is objectively better than Javascript for the task of running code in the browser, so my prediction is that Javascript will be deprecated before Webassembly.

Reply on news.ycombinator.com