Hacker News Reader

Not really “on the verge” considering how long it took to migrate most projects from Python2 to Python3. I mean, people won’t just drop existing projects, and adoption will be awfully slow.

> replacing the entire browser development stack. No more html, css, typescript, or JavaScript.

And how is it going to do that when wasm has literally no access to anything, except through browser's HTML, CSS, Javascript etc.?

Just give me a WebGPU backed canvas and I'll take it from there using the same toolkits I do for the desktop.

> a WebGPU backed canvas

WebGPU won't be available for a while. It's API is Javascript-only browser API.

Canvas are only accessible through Javascript through the browser.

Next question is: how are you going to accommodate accessibility?

that may eventually be true about JS but not really for HTML/CSS

I guarantee someone is silently working on an alternate rendering engine. When it comes out, it’ll be a massive game changer like Google Maps was.