31 ms·
> simply render their own UI simply is doing a lot of heavy lifting here. > and handle things like accessibility with their own accessibility based DOM that j
by troupo 3y ago
> simply render their own UI
simply is doing a lot of heavy lifting here.
> and handle things like accessibility with their own accessibility based DOM that just handles the accessibility
just is doing as much heavy lifting as simply before it.
> I believe this is what Flutter does.
Flutter "just" "simply" have a trillion-dollar company sponsoring their project that came out of internal power struggles. And they have "just" "simply" been working on it for 6 years, and currently has 11 thousand issues in their repository.
- satvikpendem 3y agoWell, that's why I use Flutter rather than some other community-led project in another language, like I see in Rust like Slint, because it's quite a big task to redo a lot of this work for WASM.
- troupo 3y agoYes, see how "simply" and "just" quickly became "I will only use code from a trillian-dollar corporation because it's neither 'simple' nor 'just' to build a proper UI framework"
- satvikpendem 3y agoSure, maybe I shouldn't have used those words, but my point was that it will enable a lot more flexibility for people who want to write apps across platforms and with their own preferred language instead of Javascript, because it will all compile down to WASM, as well as stopping people from bemoaning the slowness of Electron, or shipping an entire browser per app. Instead, one ships the app to the browser.
- troupo 3y ago> or shipping an entire browser per app. Instead, one ships the app to the browser. Yes. Instead you're shipping the entire app, including the whole graphical framework, with every app. To quote Figma, "Pulling this off was really hard; we’ve basically ended up building a browser inside a browser." https://www.figma.com/blog/building-a-professional-design-tool-on-the-web/ https://www.figma.com/blog/building-a-professional-design-to... Are you sure this is what you want?
- satvikpendem 3y agoIt makes writing the desktop apps easier, instead of using a separate framework for the web and another one for the desktop (which costs engineering time and money), or, again, shipping an entire browser per app (which saves engineering time and money but is a bad experience for the end user). You can't escape this complexity, there's no way around it if you want to make cross platform apps. Now if you just want to make a website or webapp (with no intention of making it cross platform), stick with the DOM, it's not going anywhere.
- troupo 3y ago> or, again, shipping an entire browser per app You're still going to ship basically an entire browser per every app in the browser. Where do you think the new glorious UI for your app is going to come from with WASM?
- satvikpendem 3y agoWhy would you ship an entire browser per app? Not sure what you mean, you just ship the application code. On desktop you use the native language code, or if you really want, a native WASM runtime that exists outside of the browser, such as Wasmer or Wasmtime.
- troupo 3y agoYes, you'd need to ship the entire app. Per every web app per every user. So, for example. The currently featured app in iOS app store is Plane Finder. It weights 99 MB. [1] So your proposal now is to ship those 99MB to every user of the web app written in WASM. However bloated we think modern web apps are, they are not even close to these numbers. https://apps.apple.com/se/app/plane-finder-flight-tracker/id361273585?l=en-GB https://apps.apple.com/se/app/plane-finder-flight-tracker/id...
- satvikpendem 3y agoYes? How do you think applications work on non-web platforms? If you want a thin client app, put all your logic in the server side and don't ship as much code on the client side, whether it be in the DOM or WASM.