Qt for WebAssembly
Oof - the point of WebAssembly is not to stick your entire UI in Canvas.This really rubs me the wrong way, it's a major step backwards for accessibility and user control.WebAssembly lets you bypass Javascript - it should not be viewed as a license to build web apps that ignore user-defined shortcuts, don't work with screenreaders, aren't responsive on mobile, can't be customized with user-defined CSS, and that can't be scraped or automated in the browser.Honestly, at the risk of sounding dismissive, I am increasingly suspecting that native developers just don't understand what the web is trying to do. The web is different from native because it's solving problems that native developers don't even realize they have.Sometimes APIs on the web are difficult because they're poorly designed. But sometimes APIs are difficult because they're solving really hard problems that developers aren't aware of. Before those APIs are thrown in the trash, we should take a step back and think about why they were built in the first place.It will be a large blow to the software industry if the result of WebAssembly is that everyone ignores large portions of what made the web great in the first place.