For a traditional programmer, this is equivalent to a (very public) proliferation of "convenience" interfaces or methods, yielding one "convenience" method for every possible combination of real method calls. With such a proliferation, these methods cause a great deal more inconvenience then they alleviate, and the situation becomes absurd. (For some reason, Twitter's Boilerplate release has spawned an incredible number of mis-guided "me too" fork-projects that basically roll in <insert technology here> into the Boilerplate project and release it as new.)

So, the serious message is that a) people need to stop with the combinatorial responsive html5 boilerplate bootstrap projects, and b) there's a real architectural problem that needs solving on the front-end of the web. Basically, we need a module system for HTML, JavaScript, and CSS. (And it's shocking that such a thing doesn't exist, apart from ad hoc, essentially proprietary solutions like WordPress themes.)

Unfortunately I cannot downvote!