CSS Resets have been growing in popularity over the years, until it's become such a standard that many tutorials guiding you through the basics of CSS even advice you to include a CSS Reset, before you do anything else! No doubt it can be useful to bridge the differences in the way browsers display different elements, but at the same time there are a few cons to this useful technique.
The big one, is that every element added to your stylesheet is a request to the browser. The more styles you include, the heavier your site will be to load. Not like it will be a noticable difference for most sites; especially not if you're using a modern computer and browser, but in the service of tweaking webpages as much as possible, styles that aren't necessary to add shouldn't be added. For example, I never use the <cite> tag, so there's no reason why I should include it in my stylesheet.
The CSS Reset I used last year had a lot of unnecessary elements in it, and a lot of necessary ones, too. When I implemented it some of the elements I had styled myself suddenly looked a bit messed up due to browser-defined margins and paddings and other things suddenly receiving a null value, so I had to redo quite a bit of code with the new values in mind. But considering I'm getting a display standard not based on a specific browser, it was worth the time it took to change.
But a CSS Reset won't fix everything. I realized while going through my stylesheet that everything I'd like to tweak doesn't need a Reset. The Reset is for the most part just a duplicate value of something I'm styling myself, and the browser doesn't interfere as much as you'd think. Since IE implemented the quotation marks for <q> tags, there aren't so many noticeable differences between them either.
It might require me to check the site on different browsers once in a while and look for bugs, but otherwise, the switch will make things both easier and faster. So, I'm skipping the reset this time around.
