Both Aaron Wormus and Henri Bergius picked up on a post over on Andy Smith's blog about why he doesn't like frameworks.

I'm a library guy, I like a big set of tools available to call upon at need, I like to have a favorite hammer and a favorite saw and know the tricks for making them both fit on my belt without running into my legs when I am working on something. Framework people like the 5-in-1 lathe-press-drill-saw-grinder and figuring out the tricks to fit the piece of wood they are working on into the machine. When you have a framework everything will be lathe-press-drill-saw-grinded into submission, and you better read the manual otherwise the machine won't even turn on.

Frameworks suck because they are an avatar of enterprise,
frameworks suck because they take away your freedom,
frameworks suck because they build walls between coders,
frameworks suck because they make you fit your project to the toolset rather than the toolset to the project, and frameworks suck because they take the fun out of programming, long live the library.

Henri and Aaron both have their opinions on the matters - support for frameworks and support for libraries, respectively. Personally, I've only started looking into frameworks, so I'm not sure that I'm qualified to say one way or another, but, given the choice, I'd be all about the libraries. Frameworks have always seemed so confining to me, forcing you to spend less time being creative with an app and more time trying to get it to work in the parameters of the framework...