4 ms·
IMO you either need to go all in or not at all. And by all in I mean your "web page" is nothing but a <canvas> tag and your non-web framework is handling basica
by afavour 2y ago
IMO you either need to go all in or not at all. And by all in I mean your "web page" is nothing but a <canvas> tag and your non-web framework is handling basically everything. It's an unholy nightmare for many reasons but it would at least allow you to make a reliable self-contained system.
"We'll take your native constructs and jimmy them into some bastardized HTML" is almost always full of razor-sharp edge cases.
- moffkalast 2y agoWell that but with WebGPU just might work without turning your app into lagtown central, in a year or five when it's widely supported anyway.
- pjmlp 2y agoWelcome to what made Flash took off in first place.
- afavour 2y agoI'm old enough to remember making admins with Adobe Flex. I unironically kind of miss it.
- Sn3llius 2y agoAgreed! And indeed we are still considering switching Rio to a Canvas + WebGL/WebGPU. The reason we've decided against it for now is accessibility, and weird edge cases such as Copy & Pasting.
- moritzwarhier 2y agoWhat about text rendering? Apart from native a11y, hackability/"DX" and affordances like text selection, I feel that text rendering is a big moat of classic web technologies.
- bobbylarrybobby 2y agoHow does a screen reader interact with one of these canvas pages?
- afavour 2y agoThat would be one of the entries in the "unholy nightmare" bullet list.
- wiseowise 2y ago> And by all in I mean your "web page" is nothing but a <canvas> tag and your non-web framework is handling basically everything What a huge step back for the web.