Web Browsers? Are They Doing it all Wrong?
Consumed => “Spring-cleaning Unused CSS With Grunt, Gulp, Broccoli or Brunch” by Addy Osmani on his blog / site.
=> My value add (i.e., left a comment)…
Great article. Thanks for sharing.
I’m curious: How do you balance this against Bootstrap (and its ilk) being used via CDN? That is, the brunt of the style.css is already cached via a visit to another site (also using the same CDN.version), and then there’s naturally a bit site-centric CSS separate from that.
Mind you, I understand that extra CSS also taxes the browser as it renders the page, but how much so? How impacted (read: compromised) or not is the actual user experience? On a large page? What about something smaller / typical?
That aside, it seems to me that the unCSS’ing is actually something that ideally should be the responsibility of the browser. The browser knows that it needs and when it needs it, so why doesn’t it have the intelligence – beyond brute force (so to speak) caching – to fine tune what it caches? And what if the browser pre-loaded (a la CDN) the top three to five frameworks?
My point being, this unCSS idea is interesting and helpful, but is it as practical and wonder as it looks? As other comments have suggested? Or are we trying to squeeze blood from the wrong stone? In the wrong way? Why are we each individually working so hard to do things that feel browser-centic?