Daevid Vincent wrote:
>> -----Original Message-----
>> From: Vishal Rewari [mailto:rewari.vis...@gmail.com] 
>> Sent: Friday, March 26, 2010 9:29 PM
>> I am vishal, I have recently started development in PHP
>> I have come across these PHP frameworks:
>>    1. Codeigniter
>>    2. Symphony
>>    3. CakePHP
>>    4. PEAR
>> Please guide me which one of them is *good in performance ? available
>> functionality ? Easy to use and configure* or the one you 
>> would recommend according to your experience.
> I was forced to use Symfony before. Hated every second of it. The company
> eventually folded, no doubt in part due to the poor decision to use this
> framework.
> For example, using the "Symfony way" of looping over various news stories,
> creating objects and the whole ORM and all that crap, it would take a
> second or so per story to process. With thousands of stories this took
> hours to process. We then said F-it and re-wrote the parser in straight up
> PHP and now the processing took a couple of minutes.
>> or should I stick to native call from PHP?
> Yes.
> Most real developers do NOT use off-the-shelf frameworks. We generally roll
> our own since no framework will do everything you're going to want or need
> for your particular project, and then your stuck either trying to wedge
> something in, or hoping "they" eventually catch up to your needs. They try
> to be all things to all people and therefore you carry a lot of baggage and
> bloat you don't want/need. And the biggest reason to avoid them is if your
> project grows, now you have to find not only a skilled PHP developer, but
> one that knows this additional framework and is proficient enough to use it
> well. It's just a hassle in the end and puts digital handcuffs on you.
> Write some wrappers for your DB calls and other useful routines and KISS.
> Frameworks are great for a quick proto-type, but IMHO, why waste energy
> when you'll just have to re-write it again for real. Do it right from the
> start.

Agreed (strangely) I've always opted for roll your own; however one
exception is zend framework, v good and nice and modular; another
exception is standard "do the job well" libraries such as reCaptcha lib,
SimplePie, some PEAR stuff and gubbins like that - often saves time and
the code is pretty solid.

Personally I find a good collection of classes I've built up over the
years fit's the bill perfectly; but then I've had the years to build
them up.

If you've got the choice and the time/budget/inclination/ability it's a
good approach to roll your own from scratch - if you don't or you're
part of a huge team then odds are it'll be picking the lightest
framework you can, which the most dev's know, to get going (java style
"urm should we use spring or ejb").

Often the get it working then optimise is a required approach for sweat
shops (ahem. sorry I mean agencies). Again though, if you are employed
always best to run the choice through management just to cover your ass.

It's all relative and on a per project / client / boss basis; and not
everybody is lucky enough to pick and choose their jobs / techs and
methods. (but I am :p)


PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to