Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

What is the best CSS Framework and are they worth the effort?

Reading on another forum I've came across the world of CSS Frameworks. The one I've been specifically looking at is BluePrint. I was wondering if anyone else had come across CSS frameworks, suggest which is the best and if they are worth the effort?

like image 611
Martin Clarke Avatar asked Oct 14 '08 22:10

Martin Clarke


People also ask

Is there a better framework than Bootstrap?

With all the perks of an advanced framework, Foundation is definitely the strongest alternative to Bootstrap. It is being used by some of the biggest organizations in the world for e.g. Adobe, Amazon, HP, eBay etc to quote a few.

Which of these are popular CSS frameworks?

Bootstrap - The most popular HTML, CSS, and JavaScript framework for developing responsive, mobile first projects on the web. Bulma - Modern CSS framework based on Flexbox. Foundation - The most advanced responsive front-end framework in the world.


2 Answers

CSS 'frameworks' are completely missing the point.

CSS is not like JavaScript, where you can include a base library/framework and then call functions and objects from it to do higher-level work. All a CSS framework can give you is declarative rules: some default browser-rule-reset stuff, some class styles to be forced to author your page to, and layout rules using 'float' and 'clear'. You can write that in a few lines of CSS yourself rather than pulling in the bloat of a hundred framework rules.

The 'grid layout' stuff in particular goes back to the bad old days of mixing your presentation into your markup. 'div class="span-24"' is no better than a table, you'll have to go back in there and change the markup to affect the layout. And all the frameworks I've seen are based around fixed-pixel floated boxes, making it impossible to create a liquid layout accessible on a wide range of window sizes.

It's backwards authoring, of use only for someone too scared to write a CSS rule.

like image 54
bobince Avatar answered Sep 27 '22 22:09

bobince


So, nobody's responded to this question yet (although I've seen a few upvotes), so I am going to at least attempt to tackle the second question in this prompt.

CSS Frameworks are great; like any other framework, they reduce development time and let you get working immediately on site-specific design and CSS. They think about hard decisions so you don't have to.

Unfortunately, there are two downsides to using a framework (in general):

  1. The framework dictates the overall structure and mechanics of your CSS code. Now, I'm not talking about a CSS reset (these are useful in their own right, but they are not true frameworks); I'm talking about an honest to good framework, that has already made the decisions about what semantic tags you are going to be using in your document, etc. As such, you are made dependent on the framework, and when there is a bug in the framework, you will most commonly have to fix it yourself.

  2. Frameworks are not an excuse for being oblivious to cross-browser/advanced CSS issues. You will invariably run into them, just as you would working with a PHP or JavaScript framework. And you need to know how to deal with them. There is a common saying that you should write your own framework first, before using someone else's.

Taking a quick peek at Blueprint, I would not really call it a framework; maybe a reset with a few extra goodies on top.

like image 33
Edward Z. Yang Avatar answered Sep 27 '22 20:09

Edward Z. Yang