This concept of “frameworks” is pretty new to us designers and CSS authors. However, it’s not new to engineers. These guys have been dealing with frameworks, libraries, and snippets since the dawn of ages, it seems. James helps to explain why, from the perspective of a programmer — a very experienced, very expert-level one — frameworks are often developed, used, and published. He talks about the advantages and disadvantages of frameworks to developers, based on of many years of computer science and frameworks being built and used for almost every computer language ever created — years that us web designers simply almost never have (most of us are not programmers at all, and certainly not serious ones who have great experiences outside the realm of simple web scripting).More
Wow. Less than 24 hours after my last post, there have been nearly 100 comments posted, and I’ve seemingly managed to piss off half the Internet. It seems some people took major offense to my thoughts, although no one has came forward to told me why (Andy Budd said on Twitter, “you’ve managed to tick off quite a few ‘limeys’ with your post,” but he didn’t answer when I asked why.
Of all the topics I’ve ever written about, I would have thought CSS frameworks would be one of the most non-controversial. Apparently, not so. I thought I’d follow up by trying to detail what I’ve learned after a century of commentary on the past in question.More
Over the past several weeks, I’ve been bombarded (in e-mail, in person, and over IM) with questions about CSS frameworks. I guess I wrote the book on this topic (and contributed, if inadvertently, to one of the most notable CSS frameworks out there), so it’s completely understandable people would come to me with these questions. The question almost always sounds something like this:
“I’ve read what you’ve written about CSS frameworks, and it sounds great…but [insert name of a usually-British CSS guru here] said they were bad. What do you think about what they have to say?”More