How CSS Frameworks should work

It seems people are still up in arms over CSS Frameworks, and specifically blue print css. Monday By Noon takes a step back and looks at the two sides of the argument.

It seems that many people take issue with frameworks due to the bloat that goes along with them, not the thought that you should have some sort of structure to help improve development time.

This could be fixed however if the boiler plate in development was modular, each section a different file based on what it does. Upon the need to launch the site included files could be combined into one to prevent the extra server requests. This could be done manually, or compiled by a program.

If someone wanted to develop said program (*hint*) it could include additional features such as compressing and combining of html/css/javascript files as well. Think of it as an all in one way to speed up any website when going from development to launching.