One interesting feature of html boilerplate was that, in its CSS, it set the background color of selected text to #fe57a1 (hot pink). For the longest time, it was a pretty easy way to identify an HB-based site as many developers didn't customize text selection. It also looked rather neat.
HTML5 Boilerplate has been around a lot longer than Bootstrap and has been adopted by more in the general front-end community. Whereas Bootstrap has been adopted by more generalist developers building entire web applications.
Very nice, will have to check this out for the project I'm starting today. Sick of using Bootstrap to demo when I usually change everything. Just need some boilerplate instead.
I don't see plugins.js and main.js loading twice. And that CSS warning can only come from other tabs you had open as we don't include any `-o-` prefixed code in the CSS.
I think these are all Opera quirks. It is saying there are unhandled exceptions when all the ones it identified are inside a try/catch. It looks the -o- warnings are coming from the internal feature detects that we use in jQuery 1.8, we really can't avoid those without browser sniffing.
Right from the frontpage (check the links over there):
"Who uses HTML5 Boilerplate?
Google, Microsoft, NASA, Nike, Barack Obama, Mercedes-Benz, ITV News, BAE Systems, Creative Commons, Australia Post, Entertainment Weekly, Racing Green, and many more."
> You usually won't know a web page is actually using H5BP, especially without looking at the source.
One of the ways to know, before the new release which sadly kills it, was that many sites didn't customize the default hot pink text-selection background color.
Select text and get hot pink? You knew it was the boilerplate.
It's boilerplate. It's sensible to assume that sites might use GA, and their snippet is more optimized than the stock one Google gives you, IIRC. It's not difficult to delete.
