That's the reason for resets. Because "browsers" could mean one of a million different browsers and it would take forever to tweak each of them, since CSS isn't the same across the board. I'd like to see some CSS that isn't using a reset that looks perfect across IE 6, 7, 8, 9, Opera X-Z, Chrome X-Z, Firefox X-Z, and Safari. Additionally, I'm guessing such CSS could probably be done faster with a reset.
Any competently written CSS will give you that without the resets and normalizers nonsense. Just normalize elements you want to normalize, without polluting your inheritance chain and making yourself pain to debug it.
I've been writing CSS for god-knows-how-many years and never ever saw the need for it. And yes, I do cross-browser sites (and that even includes Opera).
That's just too much manual work that's the same over and over again. We already know what elements are different between browsers, and reset fixes that, without requiring manual labor; it's a better approach.
Not sure who those "we" are, but reseting every damn element is far from demonstrating knowledge. Especially if it is separate stylesheet. There is nothing better in that approach at all.
Maybe if you have absolute control over the HTML that's ending up inside your pages. Mostly I work on sites where someone's going to be using a WYSIWIG or raw HTML to add content, and I have no control over what elements they use or which browsers they test in.
CSS gets re-written anyway along the way. Resets gives you a leg up in the beginning for a consistent look across browsers so you can focus on other pieces of a project -- at least that's how I use it.
