Re:WASM by Example
by itslennysfault on Wednesday November 15, 2023 @11:13AM
(#38278304)
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.
[ Parent
| on HN ]
> Nothing beats html/css for achieving that
Many people would argue that the native iOS and Android UI toolkits beat HTML/css.
6dc610bc2d7c1ba9b6783c61bf8c79897c733964e845d574990b120954428d69
They don’t run on the web, though.
ChromeOS you mean.
The website can use the toolkit by shipping it in webasm.
ae0f36b12c0a363dd4eaf94fb65b33bd7c7f55e879a85c24394d6d06d02af4d5
Why must all apps support all scenarios? Is the latest triple-A big-budget video game ADA compliant? Does it run on a 3" phone?
Re:WASM by Example
by cantSpellSober on Wednesday November 15, 2023 @04:38PM
(#38282905)
My 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-r...
> HTML/CSS/JavaScript UI around a main WASM-controlled center canvas, allowing developers to build accessible experiences
I can easily see that being abused obviously. (If anyone has any useful articles regarding accessibility and WASM please share)
Well, 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.