It's time for modern CSS to kill the SPA

Re:It's time for modern CSS to kill the SPA by matt_s on Friday July 25, 2025 @06:42PM (#44689355)

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.

[ Parent | on HN ]

Re:It's time for modern CSS to kill the SPA by wldcordeiro on Friday July 25, 2025 @07:24PM (#44689696)

Lots 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.

[ Parent | on HN ]

Re:It's time for modern CSS to kill the SPA by paulryanrogers on Friday July 25, 2025 @08:00PM (#44689939)

Is this true everywhere? Isn't much of the world still on slow mobile networks?

[ Parent | on HN ]

Re:It's time for modern CSS to kill the SPA by yawaramin on Friday July 25, 2025 @08:18PM (#44690091)

Being on a slow mobile network and having to reload changing bundles multiple times a day to use SPAs would be an even worse UX.

[ Parent | on HN ]

Re:It's time for modern CSS to kill the SPA by youngtaff on Saturday July 26, 2025 @04:48AM (#44692532)

> 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

[ Parent | on HN ]