...which "underscore"s the fact that you can make a great site prototype with frameworks (JS, CSS, etc). My claim was not that they have no use. But that you start with them, get a great site, then pull out the re-usable framework stuff and leave the customized stuff that makes your site/app so great.

It's not a prototype. It's a business that makes money.

Yeah, if it makes more money, some day, I might consider dedicating some of it to replacing the CSS framework. But it's really, really far down on my list of things to do. There are lots of improvements I could make to the UI without ditching the framework, for instance, that would add real value to my customers, and/or increase conversions.

Why would you want to remove the framework? This would just be a huge waste of effort for no gain, as the grandparent shared. A decent un-bloated framework would account most of the time to a half-assed image. Not worth the trouble.