First Impression of Zend Framework
So, if you have not heard, Zend released a preview of what they are calling the Zend Framework (ZF), http://framework.zend.com/. Check it out, I think most will see the same thing I do....
What are they thinking? Have they not been paying attention to web development progress over the last year? Are they really this thick headed?
Sure the ZF has some nice classes in it. But can anyone tell me why a class needs a method call getDir, which does not nothing but mirror the dirname() method already in php. I guess its supposed to make your code cleaner? Probably the best part of the code they released is the ZMail. That could be helpful, but brings up the larger point that has been troubling me for some time.
Why does Zend need a Framework? They are the PHP company, why do they not just write this stuff into the core of php or make a module that can be compiled. The only answer I have come up with is so they can keep up with the Jones'. Every language has a framework so PHP must have one. Well, this preview release is further from a framework than I had expected.
To me, a framework should help structure your app, allow you to write code faster, not involve require_once or include from the user perspective, and have some nice conventions that really speed up the development process. the ZF maybe does one of these things. Granted, I am still waiting to see some better tutorials beyond the provided code snippets, but still there is no inherent structure in the ZF. I look at the ZF as a component set like PEAR or ezComponents, not a framework.
Should I go into some other things that bother me? Ok, how about a class dedicated to printing an html textarea. Yes, look in /Zend/View/Helpers/ you will see some really great classes there, like one for a form button. Ok, so we can extend it woop tee do. I must be missing something huge here, cause I cannot see the advantage of having 14 seperate classes for something like html form elements.
There are somethings in the ZF that I like besides some of its components. They are pretty aggressive code commenters, which is cool. The other thing that I like is that they did nothing that would make me want to switch from CakePHP. CakePHP does the things a framework should. Its still early, but I see a lot more promise in how Cake is approaching RAD than ZF. Sure ZF has huge corporate sponsors and the backing of some old school php programmers, but who cares. CakePHP is open source, with some darn good developers of its own. I am pretty sure PHP was successful before the big, corporate sponsors decided to get involved. CakePHP will be successful cause it makes programming in PHP beautiful, not to mention teaching how to be a better coder. Maybe ZF will get there one day, but right now it does not look like the ZF will be anything more than a set of useful classes. So, I will put the ones I like in vendors and use them. Maybe I will even make some Cake components for the things that are really nice.
As always, I plan on keeping up on what is going on with the ZF. When preview release 2 comes maybe there will be something more to look at, but for now there is not much to get excited about.
4 comments
Clearly, both "frameworks" were not extracted, but architected. Which make me wonder a little bit, since ezComponents should have been extracted. They probably started clean because to be PHP 5 compatible only...
us
gwoo's posts (22)
seth's posts (21)
Nate's posts (0)
subscribe

archives
June 2007 (1)
May 2007 (2)
March 2007 (1)
November 2006 (1)
October 2006 (2)
August 2006 (3)
July 2006 (1)
June 2006 (2)
May 2006 (1)
April 2006 (5)
March 2006 (11)
February 2006 (4)
January 2006 (4)







