I've been using the Zend Framework for a couple of months now, and I think it's great. It shows a lot of promise, and I'm excited to see what's to come in the future.
Having said that, I have a couple of concerns I wanted to voice: 1) Too many top level components. Why are components like Zend_TimeSync and Zend_Measure being given top level categories? Everything else so far seems to be categorized correctly, but why are those two not under the Zend_Locale namespace? Similarly, why is Zend_Gdata not under Zend_Services_Gdata like Yahoo, Delicious and the others? Seems a bit inconsistent. 2) A lack of focus No offense to the authors that are building these components, but aren't Form Helpers, an Ajax Helper, etc. more important than a Measure class, or a TimeSync class that 1/100 developers would use? It seems like we are building some components and devoting a lot of attention to areas that most people will not need. Looking at the amount of time invested, how many people will need a Zend_Measure class as opposed to an easy way to build forms, or a simple ORM component? However, it seems as though the latter components are being pushed back and attention is being devoted to components with narrow use cases. Again, I mean no offense to the authors of the Measure and TimeSync classes, and I am sure it is great code. My concern is more with the general direction of the framework. If you look at successful frameworks like RoR, or even Symfony nowdays, they build all the things that a developer needs immediately, (MVC, Forms, etc.) and once those are done, move on to the more specialized components. Just thought I would voice my opinion on this topic. Again, love the framework, and use it everyday, but was a bit concerned with the general direction and focus. -- View this message in context: http://www.nabble.com/Too-many-top-level-components%2C-lack-of-focus-tf2627415s16154.html#a7331758 Sent from the Zend Framework mailing list archive at Nabble.com.
