On Tue, 2008-04-22 at 21:06 +0800, Kinch Zhang wrote: > On 4/22/08, Tony Marston <[EMAIL PROTECTED]> wrote: > > > > If you don't use a framework then obviously you are writing nothing but > > mickey mouse programs, and wouldn't stand a chance when it comes to > > writing > > a proper application. > > > > I agree , you couldn't avoid using a framework unless you're writing a PHP > toy application.
And I disagree. I'm just putting the finishing touches on a large multi-user asset management system, built without a framework (apart from my own collection of objects I wrote and reuse to accelerate development). 40 000 lines of code and my previous version is currently being used by banks and such. We'll move them over to the new one soon. It's taken about 3 months full-time work. But, while I think there's nothing wrong with building from scratch as long as you architect carefully before you start, I think that there's also nothing wrong with frameworks. As long as you choose the one that is best going to suit your needs from the start, it can make life significantly easier. If you're building a web site for a client, you'd be insane to not seriously consider a CMS like Drupal or even WordPress (don't laugh - it's got quite a competent plug-in system and if you're in a rush you can bang something good out the door in a day.) I'm currently building a project based on CodeIgniter, and apart from quite a rigid structure, you do most of the stuff yourself anyhow. I dumped the built-in DB object for one of my own and now development is cruising. So, my philosophy is one of choosing the tool that best suits your needs, your client's needs and your project's needs, rather than using or not using frameworks based on some preconception. J -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
