3 ms·
> 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
by 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.
- troupo 3y agoSo you're sating that users complain that they have to download hundreds of egs of Electron per each app, so your proposal is... to download hundreds of megs of app over the browser anyway.
- satvikpendem 3y agoNo, that is not my (or most people's) complaint about Electron. The main complaint is that Electron is slow, and takes up obscene amounts of memory. RAM, not ROM, is the issue. In contrast, I can have native performance via WASM, even if the binary size is large (it will get smaller over time, but even then, most people don't really care about binary size, they care about speed).
- troupo 3y agoBut I definitely don't want to load 100s of MBs for web apps. And compiled wasm cache in browsers isn't unlimited, so it will get purged, and you'll have to re-download apps again.