Predicting an enormous waste of time building UI frameworks with WASM and WebGPU I am willing to bet (inflation-adjusted) 1000$ that in the next decade, multiple teams will see the advent of Wasm and WebGPU as a perfect reason to have yet another go at a cross-plattform UI framework. These projects will claim to have "native" UI elements, but it will be obvious that the are really just rebuilding everything to look like the native counterparts (similar to Flutter). Especially on macOS and iOS, major interactions will be unsupported or implemented in wrong ways (problems will likely occur around the menu bar, keyboard navigation, and integration with OS services). Scrolling will feel off on touchscreen devices and text rendering will differ from the native look. Still, some of these frameworks will have tens of thousands of stars on GitHub and be used by major companies. I would not be surprised if these frameworks were built with Rust and be seen by many as the thing that would finally bring Rust to the mainstream. I see it as likely that in whatever language these frameworks will be written, they will introduce some weird new syntax and paradigms to accomodate a more "intuitive" (probably declarative) style of writing UI code. Meanwhile, little to no progress will be made developing techniques and frameworks to build apps that are actually better for the end user. |