Wednesday, September 12th, 2007
Last month, we posted about the Blueprint & YAML CSS frameworks and reactions to the frameworks were mixed. Some folks absolutely loved it while others considered them a crutch for non-CSS savvy developers. So should CSS frameworks be used?
Jonathan offered his opinion:
A CSS framework is a different story entirely. To me, CSS can not be framed. While many of the concepts, techniques, and ideas of creating websites with CSS can be repeated many times over, in my opinion, it is impossible to create pre-written documents that will help you in your process. CSS and (X)HTML go hand in hand. (X)HTML is a language semantic in nature, which is impossible to wrap up in the style of a framework.
as did Gary:
However this segmentation of the code base into various mini files, has benefits and drawbacks too. On the whole they are handy to work with, but very can add some real load to a server with the extra http request per page view.
Both writers do list the positive aspects of CSS frameworks and both appeared to like Eric Meyer’s Reset Reloaded baseline set of styles as a starting point for an application.
Along the same lines, Agile Ajax’s Brian Dillard discusses how CSS3 might work to alleviate some of the cross-browser layout headaches that these same frameworks try to address:
No, my favorite CSS 3 spec is the Advanced Layout Module. (Thanks to my buddy Zack for alerting me to its existence.) This “concept album” exploring advanced layout strategies recently received its first refresh since 2005 (discussion here). For anybody who’s ever struggled with CSS layout, there’s a lot to love in this proposed templating system. Basically, the spec calls for a new type of display that combines the best aspects of table-based and float-based layout but provides far more flexibility than either.
Posted by Rey Bango at 6:00 am