Interview with Matthew Weier O’Phinney Posted on February 21, 2012December 13, 2016 by Cal Evans @weierophinney Audio https://media.blubrry.com/vote/elephpant.s3.amazonaws.com/vote_040.mp3Podcast: Play in new window | DownloadSubscribe: Google Podcasts | Spotify | Stitcher | RSS | More Show Notesfunkatron.com/posts/the-microphp-manifesto.htmlgroups.google.com/group/fsd-phpakrabat.com/zend-framework-2/using-zendloaderautoloadermwop.net/blogTweetShare
5 thoughts on “Interview with Matthew Weier O’Phinney”
It sounds like ZendFramework2 is taking a few pages from Symfony2’s book: event-driven architecture, DIC across the board, bundles (well, ZF calls them modules), and annotation configuration support. Heck, they are even refactoring good ol’ Zend_Form, famous as it is, to be more like Symfony\Component\Form – validation will occur in the model and not be configured directly into the form. While I wish the wheel wouldn’t be invented this many times, I have to believe that multiple implementations for the same problem, however similar, are a good thing. On the other hand, I wish these communities could look at the Rails world and learn to work together (take for example, Rails & Merb) 🙂
Actually, the “re-invented” pieces are slightly different and more abstract.
Symfony2 did a great job in getting all that stuff working, but I’m in the Zf2 world since a couple of months now and I can say things are set up cleaner and in my opinion better.
Also, the new Module system is quite Framework agnostic, which would probably allow to build a bridge filling the gap between Symfony and Zend.
I like the direction that was taken, and things changed a lot, especially about community 🙂
Also, components have been decoupled quite a bit, so dropping the framework in existing projects should become easier and easier.
About the rails approach… well… both Symfony 2 and Zend Framework 2 don’t really aim at that. You could check Symfony RAD edition by KnpLabs if you want a more rails- oriented approach: https://rad.knplabs.com/
The only real pitfall (should be fixed before stable) is performance issues with the DiC container, which is a bit slow in discovering dependencies…