3 ms·
It's cute but I think the ramifications for left over CSS are pretty insignificant except in some very rare edge cases. It would be cooler if you could feed it
by benologist 17y ago
It's cute but I think the ramifications for left over CSS are pretty insignificant except in some very rare edge cases.
It would be cooler if you could feed it a CSS file and have it return a better version of it, well and concisely formatted without redundant declarations, using shorthand etc.
That would take this from something that doesn't really need doing - like css minification in a world where gzip exists, such as our world - to something that would show people a better way to produce CSS and still retain that original functionality if you're convinced there's a need for that.
- mnemonik 17y agoI think there are 2 main benefits: 1.) Maintainability. Promote re-use of selectors and organization of your css files. I find that CSS gets sloppy very quickly and there will be lots of non-DRY, redundant selectors, as well as legacy selectors that no one will ever remove because "what if something is still using it?" Your css files will slowly get larger and larger, and never smaller. This leads to the next point. 2.) Smaller file size. Less bandwidth used, faster requests. Yahoo has done a ton of research on the benefits of performant web apps: http://developer.yahoo.com/performance/rules.html http://developer.yahoo.com/performance/rules.html