3 ms·
Nah, that is a nightmare. Don't forget your WebGL/Canvas based UI has to be responsive to screens ranging from a 3" phone up to a 8K ultrawide monitor. Nothing
by itslennysfault 3y ago
Nah, that is a nightmare. Don't forget your WebGL/Canvas based UI has to be responsive to screens ranging from a 3" phone up to a 8K ultrawide monitor. Nothing beats html/css for achieving that. Also, good luck with ADA compliance when your page is a pixel drawing on canvas.
- Jyaif 3y ago> Nothing beats html/css for achieving that Many people would argue that the native iOS and Android UI toolkits beat HTML/css. 6dc610bc2d7c1ba9b6783c61bf8c79897c733964e845d574990b120954428d69
- recursive 3y agoWhy must all apps support all scenarios? Is the latest triple-A big-budget video game ADA compliant? Does it run on a 3" phone?
- cantSpellSober 3y agoMy understanding is that devs are "supposed" to use WASM as a compliment to a11y-friendly tech. From https://webassembly.org/docs/faq/#is-webassembly-trying-to-replace-javascript https://webassembly.org/docs/faq/#is-webassembly-trying-to-r... > HTML/CSS/JavaScript UI around a main WASM-controlled center canvas, allowing developers to build accessible experiences I can easily see that not happening obviously (plenty of non-WASM sites with poor a11y exist already). If anyone has any useful articles regarding accessibility and WASM please share.
- kaba0 3y agoWell, there is Flutter, which is no small project, that renders to the web (always promising to go dom-based) — and it’s still just a canvas with zero accessibility. So if google doesn’t have the resources/priorities for that, I doubt that 2-person rust library will.
- pjmlp 3y agoIt is the revenge of plugins, after we got a 10 year delay with WebAssembly re-inventing the stack.