3 ms·
> and just rendering their system via one big canvas element Interesting perspective, but I'm not sure if this would really solve the problem. You'd have to im
by WA 3y ago
> and just rendering their system via one big canvas element
Interesting perspective, but I'm not sure if this would really solve the problem. You'd have to implement so much functionality that we take for granted (selecting text, copy & paste, accessibility, keyboard shortcuts, etc.). If you don't want to do it yourself, you have to use a widget library or some kind of UI kit. Maybe like Flutter. The web-version of a Flutter app renders everything to canvas (with a lot of caveats).
Since people bring their own UI libs for their JS-CSS-HTML web apps all the time, they will probably do the same with a pure canvas implementation and the result would be even shittier, because half of them will forget basic functionality.
- lmm 3y ago> You'd have to implement so much functionality that we take for granted (selecting text, copy & paste, accessibility, keyboard shortcuts, etc.). If you don't want to do it yourself, you have to use a widget library or some kind of UI kit. Maybe like Flutter. The web-version of a Flutter app renders everything to canvas (with a lot of caveats). > Since people bring their own UI libs for their JS-CSS-HTML web apps all the time, they will probably do the same with a pure canvas implementation and the result would be even shittier, because half of them will forget basic functionality. The thing is that it's much easier for a UI lib to fix missing functionality than a browser. And when the fix is ready, the webdev can bump the dependency and then it's fixed for all their users, rather than having to hope that it somehow makes it through their vendor's update process. So even if the UI libs are initially worse, I'd expect them to overtake the browser builtins pretty quickly.