3 ms·
You're missing the point here. The author is not looking for normalize.css, but advises against such nuke-it-from-the-orbit approaches. It's just 5 rules, beca
by pornel 8y ago
You're missing the point here. The author is not looking for normalize.css, but advises against such nuke-it-from-the-orbit approaches.
It's just 5 rules, because you don't need more. And you can copy'n'paste them if you don't want to bother with npm.
- yoz-y 8y agoThe reset parent posted does better job of explaining what it does than this micro reset. Which is something the author advocates. I agree with him that you do not need to use rules that do not apply on elements you don't use. However, the multi cascade can be handled by a css preprocessor.
- rootlocus 8y agoYou mean the original author doesn't need more? I'm all for minimalism, but my minimalism doesn't necessary mean everyone's minimalism. And while the readme mentions you might not need it, or you might need to add to it, IMHO if it's not something that meaningfully solves the problem for a majority of users, and if it's trivially small then it probably isn't that useful.
- fortyseven 8y agoSo... guess you don't use it then, eh?
- birdtime 8y agoIt's not really useful, no. But it's interesting. I read the readme and the five lines of code as a blog post. It makes a couple good points. First, there's no need to reset elements that aren't being used. Second, a reset file is redundant by nature since it's overwriting a "reset" provided by the browser, that's subsequently overwritten by any custom styling. But yes, in virtually every scenario it's more practical to not think about it and use normalize.
- dosy 8y agoAlways appreciate a good Aliens reference. Especially when it's helping point out what the parent didn't understand about the approach. I think a minimal set of cross-browser CSS reset rules is a very interesting thing.