Any designers/developers use the blueprint css?

I used it for around two or three sites I created then dropped it. The fact of the matter is that CSS is so easy (for me anyways) that I see no point in using it. I have a general layout that I like to keep in my CSS files so I use my own CSS “framework” I guess. If you’re a complete CSS noob then yeah, I guess blueprint CSS would be a good start to help you get away from tables.

The only reason I can see for a professional designer (who is worth her salt at least) to use Blueprint is for rapid prototyping. Otherwise, it’s way too constrictive. Plus, doesn’t it have like 6 HTTP requests?

I don’t like it personally, I find that when building a website that’s a.) going to work in all the browsers, and b.) is very unique. A grid is simply to constructive (as irondavy said). That’s just my two cents.

I don’t like it at all, and don’t think that it would help a learner, either. Blueprint doesn’t really resemble CSS anymore.

Thanks guys.

Overshard, any chance you would like to share your custom framework or is it top secret? :)

@pixelkid74 It is nothing special, It is basically just a bunch of random bits of code that I have to fix things that annoy me in browsers like IE. Just take this for example, http://developer.yahoo.com/yui/reset/ , and redo it to suit your needs. Then go through and develop the rest of it yourself to suit your style. Every designer has a different style and if you just copy someone else you usually get called out pretty fast.

What I don’t like about it is that it requires you to add attributes and sometimes even tags to your HTML that have nothing to do with the content, i.e. there’s no semantic value in it at all. I might use the typography part some time, because I kind of suck in designing that.