Rachel Andrew writes about the explosion of boilerplates, polyfills, shivs, crazy conditional comments, rare or uneccesary meta elements, and so on—suggesting that we’re solving problems we don’t have yet. This creates pages that are fatter than they need to be and might inadvertently cause a bug in your frontend code. From the article:
“So make sure every bit of code added to your project is there for a reason you can explain, not just because it is part of some standard toolkit or boilerplate.”
Paul Irish talked about HTML Boilerplate and similar projects recently on Web Ahead and described it more as a way to spread best practice solutions to common problems not as a cut and paste solution. I get that Paul doesn’t want people to cut and paste, but the fact is that they do. (Eric Meyer expressed similar surprise when people copied CSS Reset verbatim.) The key is to know why something is used and be able to explain why you used it and where. This is the missing piece for many implementations of these boilerplates.