Why do you use framework X?
warp: I'm not a fan of frameworks, if their particular philosophy fits with the way you think, they're probably great.  For me, they just don't seem to fit and provide a lot of bloat.I prefer to start small, and add libraries as I need them.For example, for my current project I was at the point where I needed to add authentication/authorization, preferably with openid support and fallback to a simpler system for development/test installs.  I've been able to implement most of this with very little effort by using repoze.who and repoze.what (python).  They're flexible enough to do a few things which would be harder to do in a framework where components are written to interface with other parts of the framework, instead of being really generic.Apart from those two libraries I use beaker for sessions, werkzeug for dispatch, couchdb as a database, mako for templating, my own forms library, etc..Basically I put together my own framework from already existing components, with a few components of my own for those tasks where I feel the existing solutions aren't good enough or don't solve my problem.With this approach it does take longer to get up to speed, but you're not tied to any particular way of doing things and can replace any part as needed.