4 ms·
Not a fan of this bundle size, but it's not a web store landing page — it's a professional application, and it's users are likely to use it extensively through
by golergka 2y ago
Not a fan of this bundle size, but it's not a web store landing page — it's a professional application, and it's users are likely to use it extensively through their day, and all hundreds of navigation events and new tabs will (if handled correctly) hit the same cached bundle.
- notpushkin 2y agoIt’s a good point, but keep in mind that’s 32 MB of code: you can cache it, but you still have to parse and initialize it for every tab. (It might not be as bad as it sounds, WASM is lighter in this aspect than JS; but it’s still a good proxy for startup performance IMO.) It should work well for applications with longer session size, like Figma: you open a project one time and work on it for hours. I’m not sure if that’s the case with Dagger Cloud: you might be looking at a single trace, or compare dozens of builds throughout the day. The post only claims “better overall performance and lower memory usage”, but without any numbers it’s hard to tell anything.
- gedw99 2y agoI use golang WASM and use web workers and shared workers with a service worker. This means that a new tab does not reload the whole thing each time. Once you get it going it’s easy to build large complex systems.