Hi Andi, I agree with you that breaking the distribution is not the solution. I also agree that one can significantly reduce the size as you've mentioned by deleting unwanted sections but then the concern would be that the person is modifying the framework distribution and cannot be 100% sure that what he is doing will not have a negative effect. What I'd rather propose is releasing a light version of the framework that focuses only on the very basics of any web application; you dont have to to consider ajax or soa or web services or internationalization or any of the overwhelming features that the full framework has. The reason behind this opinion is that when someone sells web products, they want the overall size of the application to be in proportion with its function. For example, if the functionality of my product can be achieved in 400Kb using naked coding, I wouldn't want its size to exceed 4Mb using a framework. On the other hand I feel compelled to use ZendFramework because I want my code to adhere to the standards it sets. And because using a standard framework will make it easy for anyone to customize / tailor my product to fit their needs because the framework is well documented. I hope you can see the problem from my perspective.
Thanks, Zuhair Naqvi. Andi Gutmans wrote: > > Hi Zuhair, > > One of the benefits of the Zend Framework is that it delivers both a > hollistic piece of software which is well tested and released together > and at the same time employs a "use-at-will architecture". So I think we > deliver the best of both worlds. I would not want to break distribution > into bits and pieces as I think it would reduce the value of shipping > one piece of code that's easy to distribute which is fully tested and > supported. It also allows you to do more structured upgrades from > version to version where the main Zend Framework directory would just > need upgrading (with an easy way to rollback). > > If you are really concerned about size of download/installation then > nuking tests/ and locale/ will shrink it to about 5MB (~1.5 MB > compressed). I doubt this size would really be an issue for anyone. > > Andi > >> -----Original Message----- >> From: Zuhair [mailto:[EMAIL PROTECTED] >> Sent: Friday, July 20, 2007 9:57 PM >> To: [email protected] >> Subject: [fw-general] ZF is ubeatable BUT... >> >> >> Zend Framework will certainly bring about a major paradigm >> shift in the PHP spectrum and I am very impressed by the >> quality of code it offers BUT the only thing that has been >> discouraging me from adopting this remarkable framework is >> that it wants to become yet another pear library. I want all >> my code, including the framework to be an integral part of my >> application. In effect, I make sure to the extent possible >> that the only dependency to my application will be PHP >> itself. This is where the size of ZendFramework comes into >> play. Let's say that I am developing an e-commerce product >> which I want to sell and I want it to work out of the box on >> any standard PHP5 hosting. In this case, I cannot afford to >> have 120MB of framework code where as my actual application >> code is hardly 2MB. The zend-framework must provide an option >> for the users to pick and use one or some of its features >> independently so that I can get away with picking only the >> MVC, DB and AUTH parts and greatly reduce the code overhead. >> >> Correct me if I am wrong. >> -- >> View this message in context: >> http://www.nabble.com/ZF-is-ubeatable-BUT...-tf4120835s16154.h > tml#a11719532 >> Sent from the Zend Framework mailing list archive at Nabble.com. >> >> > > -- View this message in context: http://www.nabble.com/ZF-is-ubeatable-BUT...-tf4120835s16154.html#a11728771 Sent from the Zend Framework mailing list archive at Nabble.com.
