With symfony

Three year after i got first project on symfony. While there are always be a discussion for real value for frameworks in php comparison to core scripts. But i think when we talk about strong oops and design pattern level programming then we got best of these found in frameworks.
Symfony is one of very strong and yes complex framework in php.
It support various features like mvc, url rewriting, orm, configuration based architecture, various security features, 3rd party and user plugins.
I am most impressd with its yml based configurations. Which is overridable between different layer of architecture. So application level configuration can be overrude at module level and also on action level. Strong OOPS based architecture make code reuse easy.
It have some complexties like command line based module, models etc generation. But that all part are going easier after you doing it more times.
Well but one thing which is good and annoying both is hydration which is complex and make sometime more tough to work on complex queries.
But as my experience on working on cms like drupal is not much enjoying, it is more enjoying to play with oops and orm concepts on framework.
Well for today just that, i will dig more into symfony in incoming days.

CMS usability. A core programmer view

After a long gap i am return to blog. Last time i am here talking about synfony and linux. Now i working on drupal cms for since last six months.
It is always a question in front of a php person if using a cms compared to framework or core programming is good approach.
While cms are good RAD tools. You can make applications in few days/week which will take month to complete using core or even framework.
Cms are also very rich through their plugin system. So  customizaton is easier if using fine plugins.
They have the advance cache management.
But not all things was cms is not right. They are very unflexible to their architecture. Customization is not always easy. Some time small functionality requires big work to done.
They used database for load all content which includes html also. So even small application have big db space.
Caching is just not a feature but a requirement even into development period. This can be a advantage of frameworks which can work without caching in development mode as they use only required db space.

So in case of complex projects it is not always wise decision to use cms. But project have requiring good content management and little customization are better suitable to cms.