Well, yes. But the whole point of using a framework is that it's already created. The next time I go to a client who wants a scalable international web application that needs... well, the same stuff that's in pretty much every other scalable international web application. Why shouldn't I run it up on a framework that provides all that and save myself (and the client) six months of building, glue code, integration, and all the other testing?

One of the arguments against frameworks is that they're hard to learn: On the upside, while frameworks often need the be “learned”, this is less so the case with libraries. People read whole books on how to use a particular framework, but they usually just start programming against a library.

Right. So I go and learn a framework, once. In a few weeks of not being visibly productive, I front-load the next 2-5 years of my life and my actual day-to-day job of creating the unique stuff -- the business logic, data tier, front end -- becomes much more productive.