I'm mainly a backend guy but do some frontend work from time to time. I keep seeing all this talk about a dozen different CSS "frameworks", and I just don't get it. Can someone explain to me what the purpose of these things is? Bootstrap's site for example doesn't even try to tell me what I would want it for, it just says I want it "because its for nerds" (do I have to dress in faux-nerd chic and live in the valley t…
What you seem to be missing is that implementing complex designs means spending a lot of time dealing with cross-browser issues and platform-specific minutiae. Using these frameworks saves a lot of time, if the affordances you accept by using them are okay for you. Yes, it is a lot of boilerplate CSS. "Boilerplate" just means the boring stuff that's the same every time and is appropriately abstracted away in a framew…
No, just that using the word "framework" in reference to something that is in no way even remotely like a framework caused much confusion. I was expecting it to be a framework, and was trying to figure out what I was missing. If the answer is (and others have already said this is the case) "its just a design to copy" that's fine. Although I do find it pretty absurd that so many people seem to want to suggest that "a default stylesheet" is some revolution in web design, and is a "framework". Hasn't everyone already used their own default stylesheet since the 90s?