Too often we see code hyped up as "frameworks". But when it comes to applying them to real-world situations, they fall short and sloppy or at the other end of the scale - are huge beasts that behave like control freaks - which make them unusable or hostile to average programmers.
Some are touted as frameworks yet they act simply as front-end controllers which do nothing more than route URLs to classes, functions or include files. They make programming a bit easier, but lacking in many MVC aspects. Some require a fixed directory structure - an open invitation to hackers. Other procedural frameworks use method chaining (which can be quite long), you'd wonder at times what the right sequence should be. Some are just too bloated with so many features than you'll ever need to use in simple blog or wiki applications.
Most frameworks brag about being "lightweight" - which seems to be a relative term. Does a 50MByte framework that consumes a lot of resources qualify as lightweight? Let's call a spade a spade. A cargo truck is lightweight compared to a jumbo jet. Indeed. But if all we need to do to get from here to there on a "regular" basis is a car with some room to spare, why ride the space shuttle? Extra features are more often overkill, like using a jackhammer to drive a half-inch nail.
It seems like in the name of "improving" their software, developers simply forgot or ignored the fact that frameworks are meant to support structures, that is, make applications easier to fabricate and provide order along with industrial strength - not to be imposing structures themselves. This point is argumentative and has been going on since the days of the pyramid builders. Architects and engineers have gone thru endless debates because the first is focused on artistic freedom, the latter on structural integrity.
At the other extreme, the term "lightweight" also means a framework lacking in features that count the most. So it becomes necessary to integrate a lot of third-party modules just to make up for the most important ingredients.
Whichever the case may be, balance and minimalism in framework design - where elegant architectural patterns, engineering excellence and Formula-1 performance are available - is not a philosophy that's commonplace. However, it does manage to find its niche here and there.
This is where the PHP Fat-Free Framework makes its mark. The minimalist framework is so rooted in its Zen world of construction components, that an entire Web application can be developed in so little, yet streamlined, code. That of course means a lot when we're talking programmer productivity and time-to-deploy.
Fat-Free gives you a lot of freedom. It won't change your programming style, only your habits - albeit due to the powerful tools you'll have at your disposal. Despite that, Fat-Free is certainly not an end-all, be-all framework. It's not for everyone - only for those who want raw power behind simplicity.