4 ms·
Web Assembly capabilities are on the verge of replacing the entire browser development stack. No more html, css, typescript, or JavaScript. One of the best out
by ChicagoDave 4y ago
Web Assembly capabilities are on the verge of replacing the entire browser development stack. No more html, css, typescript, or JavaScript.
One of the best outcomes would allow app developers to avoid app stores and still provide native-like user experiences.
- laerus 4y agothat may eventually be true about JS but not really for HTML/CSS
- ChicagoDave 4y agoI 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.
- esjeon 4y agoNot 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.
- dmitriid 4y ago> 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.?
- nsb1 4y agoJust give me a WebGPU backed canvas and I'll take it from there using the same toolkits I do for the desktop.
- dmitriid 4y ago> 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?