3 ms·
But 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-
by troupo 3y ago
But 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.
- satvikpendem 3y agoFortunately this is a problem that can be solved the same way as regular desktop apps, ie not purging but having a diff based auto updater.
- troupo 3y agoApps have no control over the browser's compiled cache. If it's, say, 300 MB, 3 apps will be over that limit, and the fourth will purge at least one of them.
- satvikpendem 3y agoDo you really believe that browser makers will not implement optimizations if we start getting pure WASM apps? They will add long term storage of the app binary, auto updates via diffs, data streaming, etc. Think of them as desktop apps, but they just run in the browser instead. Why not just use desktop apps you ask? Well, people apparently don't like desktop apps, they want to work in the browser, so we have come to this roundabout way, using WASM.
- troupo 3y ago> Do you really believe that browser makers will not implement optimizations if we start getting pure WASM apps? They've already done that. That's why compiled wasm storage exists. Streaming, diff updates etc. are not the property of the browser, but of the app. And, again, browsers cannot have unlimited storage for downloaded apps. > Why not just use desktop apps you ask? Well, people apparently don't like desktop apps People do want to use desktop apps. Instead of actual desktop apps we get shitty web apps running on Electron.
- satvikpendem 3y agoI think you are missing what I'm saying. At the end of the day after this WASM business gets settled, the browser will just be the runtime for WASM apps. Nothing will be stored "in the browser," it will be stored on the user's file system, so I'm not sure why you say browsers won't have "unlimited storage," they'll be able to access as much storage as they need, same as downloading a desktop or mobile app. When WASM becomes popular enough, browsers will indeed implement streaming and diff update optimizations, just as HTTP 2/3 does today for DOM based sites and applications. Browsers will become the unified runtime for WASM apps, so they will support the common operations and optimizations for such apps. > People do want to use desktop apps. Instead of actual desktop apps we get shitty web apps running on Electron. Yes, that is my point. WASM will make these apps fast because they are actually compiled rather than be interpreted by the JS JIT as well as shipping an entire browser per app. I am honestly not sure what you're arguing for. You talk about shitty Electron apps, which I agree with, but then don't seem to have a solution, which in my case is WASM apps on the browser or via a runtime like Wasmtime. What is it that you actually want?