Geek Answers Handbook

What are the arguments against using the CSS Framework?

Yesterday I asked a question here that received more momentum than I thought. Here is the link as it is related. I'm now interested in the possibility that sharing two frameworks would be worse than using a JS framework and CSS from scratch or vice versa.

The question is obvious, if you think there are arguments against using a CSS framework like Blueprint CSS , please tell me what you think.

0
source share
3 answers

The main argument is that CSS is not a programming language. The frame is intended to include reusable functions and data structures. CSS does not have any of these constructs. The CSS framework is more like a template in a word processor. It provides ready-made design work, but also creates more restrictions than starting from scratch.

By the way, this is what led the development of Compass . It is similar to the CSS structure, but instead it uses the CSS Sass metalanguage , which has functions and variables. Thus, instead of (for example) having columns baked in the framework, you can write something like this +columns(5) +column-margins(1em)and it will generate the appropriate CSS.

+2
source

? IE6 1/3 , . CSS.

0

I use the YUI CSS libraries, but I'm not sure if this is considered the foundation.

YUI processes the basics of fonts, layouts (grids), and other formatting and makes them consistent between browsers and operating systems. It is also licensed under free software.

They also have a very useful interactive mesh constructor .

0
source

More articles:


All Articles