←back to thread

303 points vyrotek | 2 comments | | HN request time: 0.414s | source
Show context
mnemonet ◴[] No.45899976[source]
It's a nice idea, but the execution is taking the wrong path in my opinion. By rendering everything to a `<canvas>` they're sacrificing any hope of accessibility and compatibility with browser standards for UX.

I would have much preferred a React-Native-style approach, where they render to true HTML instead. Even then, WASM files are too heavy for quick loading times without good internet (and sometimes even with).

The projects I see that would most benefit from something like this are complex internal apps that need to be used in different places but aren't worth porting over/rewriting, but they would also suffer from terrible UX given the constraints of this design.

For all other projects, it makes for more sense to use React Native.

replies(1): >>45900712 #
1. cryptonym ◴[] No.45900712[source]
It's not meant to be an HTML renderer. That's for .NET apps. While it's cool they can run in a browser, that's not meant to build websites.

Would you complain that Qwasm/Dwasm doesn't follow HTML standards of accessibility?

replies(1): >>45903420 #
2. samspot ◴[] No.45903420[source]
Accessibility is for all user experiences, not just websites. WCAG is still a good resource for native apps even where some specifics do not 100% apply.

If Qwasm is referring to Quake, it absolutely should have, for example, legible color contrast and be usable if you are colorblind.