4 ms·
If you work at a place that has a modern CI/CD pipeline then your multiple deployments per day are likely rebuilding that large bundle of JS on deploy and inval
by mattbrewsbytes 1y ago
If you work at a place that has a modern CI/CD pipeline then your multiple deployments per day are likely rebuilding that large bundle of JS on deploy and invalidating any cache.
HTTP 2 has been adopted by browsers for like 10 years now and its multiplexing makes packaging large single bundles of JS irrelevant. SPA’s that use packaging of large bundles doesn’t leverage modern browser and server capabilities.
- wldcordeiro 1y agoLots of SPAs now are code-split too for what it's worth so you shouldn't really have large bundles to download if you're splitting things well.
- paulryanrogers 1y agoIs this true everywhere? Isn't much of the world still on slow mobile networks?
- yawaramin 1y agoBeing on a slow mobile network and having to reload changing bundles multiple times a day to use SPAs would be an even worse UX.
- youngtaff 1y ago> HTTP 2 has been adopted by browsers for like 10 years now and its multiplexing makes packaging large single bundles of JS irrelevant H2 doesn’t make packing irrelevant… there’s still an IPC overhead with many small files… and larger bundles tend to compress better (though compression dictionaries might help here) Large Js bundles are a huge problem though