4 ms·
So, for your webpage to start it has first to download a 1.74Mb component? Just because "it is cool"?
by diego_moita 4y ago
So, for your webpage to start it has first to download a 1.74Mb component?
Just because "it is cool"?
- aledalgrande 4y agoHave you seen how much you need to download to make Figma work? Not saying that every page should be like that but...
- deleted 4y ago[deleted]
- noveltyaccount 4y agoIt's a proof of concept, and yes, it is cool. HN can be so critical sometimes, sheesh.
- quickthrower2 4y agoImagine a line of business web app, where once you are logged in and use the app it downloads this. How is this much different from downloading a desktop app that needs to download a few meg of libraries. It definitely is not needed for blogs, wikis, news sites etc. This would be for web applications.
- panzerboiler 4y agoNot because "it is cool" but because it needs that code to operate. Consider this scenario, even for a classic website/blog: you can eagerly download all of the textual content at first load as markdown, cache it in the ServiceWorker together with a markdown parser, and go offline. You can then ask the network, if available, only for downloading images that then get added to the offline cache. Even with a spotty and slow mobile connection, after the initial load you are done with the network and you can read all the content in an efficient, environmental friendly and fast way. When the network is available, you can check if there are updates by sending a small request to the server, and update the cache.
- nymanjon 4y agolol, I thought since it was Rust that it would be like 100k or something. I think C# has it's WASM package down to 1MB or so. The implementation I did with just JS is about 50k or so, total for the app and everything. That is a bit disappointing.