4 ms·

Agreed, I think the web was simply first in being a highly versatile, capable, and relatively cheap to develop with cross platform UI toolkit. I’m much more op

Agreed, I think the web was simply first in being a highly versatile, capable, and relatively cheap to develop with cross platform UI toolkit. I’m much more optimistic about the future of native apps, the best ideas from the web are already making their way into Rust and the recently announced .NET MAUI, and with WebAssembly I think we’ll start to see native performance on the web instead of the other way around.

nicoburns 6y ago
> with WebAssembly I think we’ll start to see native performance on the web instead of the other way around. I wouldn't be so sure about that. WebAssembly doesn't do anything to help the rendering bottleneck. To do that you really have to replace (or innovate in some way) the DOM.
- russli1993 6y ago
  I think the approach many is taking is just put a canvas and draw on top. Internally, you may end up creating another DOM like structure to store all your objects. The worst thing about this approach is that you lose all browser's native support like accessibility. I think Flutter is using a combination of DOM, CSS and canvas.
  - nicoburns 6y ago
    Sure, but at that point it's not really "web" anymore. You're just writing to a WebGl or WGPU canvas, which you could do just as well from a "native" app.
  - icedchai 6y ago
    So we've basically reinvented Java applets - 25 years later.