I've always thought resetting by using a scalpel would be better than resetting by using a machete. But the problem with the scalpel is, you have to know how and where to cut. So thanks, Boilerplate guys, for figuring out where to cut!
I've never liked CSS resets, but I went through every line of normalize.css and have sinced used it on several websites, and love it. It is an incredibly well-researched and thought out stylesheet, but more importantly, every decision is justified and cited in the comments, so you can make up your own mind quite easily.
Question from someone who is not an expert in crafting CSS: Is normalize.css something that needs to be actively maintained as newer (versions?) browsers come up or older browser have some changes ?
It sounds to me that CSS Reset might be a "bulldozer" and is absolutely inelegant, but I would not have to download a newer version of it every 6 months as I probably would have to do with normalize.css. Am I missing something here ?
Good question. Even CSS resets undergo changes over time (Eric Meyer has adapted his reset several times). But resets are more limited in scope. Normalize.css includes things like: consistent `abbr`, `mark`, `svg` styles; improved `font-size` and `font-family` inheritance for forms and pre-formatted text; and fixes for a few IE, WebKit, and Firefox bugs.
Their approaches are different. But I don't think you'll need to update it regularly - just at the start of a project.
If we assume old browsers won't have new versions and newer browsers will be getting closer to the standard then I don't think you need to keep updating your code. Old simple CSS code usually works great on newer versions.
Lots of good changes! I like the standard of prompting for installing Chrome Frame for IE6 users. Gives them the option of installing the Chrome Frame or still getting to the content!
We see a future where these two projects _probably_ merge, but not just yet. I think the mobile-first, one-web community has a little more work to tackle. For now the mobile boilerplate is ideal for mobile-only webapps (like with PhoneGap).
Welcome to HN. Don’t worry about any downvotes to your first comment, but do keep in mind we tend to discourage comments that don't add anything — sometimes even if they are kind and positive, as your was. Check out the FAQ for more guidelines.
here we go again people complaining about the boilerplate having too much stuff. I would rather have this than <!DOCTYPE html> which I already know by memory.
You can always remove stuff as you please.
Can you guys accept it as a cool project that saves you time? or does the name "boilerplate" bother you that much.
[+] [-] trebor|14 years ago|reply
[+] [-] dwolfson20|14 years ago|reply
[+] [-] ZoFreX|14 years ago|reply
[+] [-] sandGorgon|14 years ago|reply
It sounds to me that CSS Reset might be a "bulldozer" and is absolutely inelegant, but I would not have to download a newer version of it every 6 months as I probably would have to do with normalize.css. Am I missing something here ?
[+] [-] necolas|14 years ago|reply
Their approaches are different. But I don't think you'll need to update it regularly - just at the start of a project.
[+] [-] iaskwhy|14 years ago|reply
[+] [-] joshfinnie|14 years ago|reply
And very interested to try out normalize.css...
[+] [-] ozten|14 years ago|reply
To plenty of corporate machines... this will be an annoying piece of bling.
[+] [-] alwillis|14 years ago|reply
[+] [-] andrewheins|14 years ago|reply
I wonder if they're implying we should use html5 v2 for mobile now. I know v2 has a "mobile-first" focus...
[+] [-] paulirish|14 years ago|reply
We see a future where these two projects _probably_ merge, but not just yet. I think the mobile-first, one-web community has a little more work to tackle. For now the mobile boilerplate is ideal for mobile-only webapps (like with PhoneGap).
[+] [-] necolas|14 years ago|reply
[+] [-] verekia|14 years ago|reply
[+] [-] alanh|14 years ago|reply
[+] [-] MostAwesomeDude|14 years ago|reply
[+] [-] pacomerh|14 years ago|reply
You can always remove stuff as you please. Can you guys accept it as a cool project that saves you time? or does the name "boilerplate" bother you that much.
[+] [-] ErikRogneby|14 years ago|reply