CSS resets are extremely useful and there is little need to reinvent them every time you make a page. A lot of people will eventually come up with their own ba

CSS resets are extremely useful and there is little need to reinvent them every time you make a page. A lot of people will eventually come up with their own base typography rules at some point as well. And grids are extremely helpful in eliminating some headaches and speeding up development. These are all components of most frameworks. None of these "frameworks" do much of anything besides some routine stuff that saves your some start up time. Telling everyone that they don't need them is a bit ridiculous. If it saves you time, makes your life easier, or have some other benefit to you, they are worth your time. For example, 960 isn't a "framework" in the same magnitude that RoR or JQuery is a framework. The problems that a CSS framework solves are much smaller than most other frameworks. 960 took all of 10 seconds to figure out and has been helpful in quickly tossing page layouts together. It has shown itself to be very reliable across browsers and certainly beats having to test your CSS layouts on IE, Firefox and Safari. The constant edit-save-refresh CSS testing cycle is a lot easier with a CSS reset and manageable grid system. Also, with 960, you aren't running away from CSS. You still need to know CSS to do anything useful with it, it just solves a few immediate issues with CSS and then gets out of your way.