NYCPHP Meetup

[Rick Olson]

Sorry for this incredibly short answer, but I'm a tad rushed... (  so no 
reasoning either =(  )

We use Symfony at my company.  Large scale, high traffic.  It's a bit 
buggy, a lot bloated, and the slowest thing I've seen in some time.  I 
don't recommend porting over to it.  Sorry :\  One really big reason for 
this is their use of ORMs.  If you just avoided Propel or their soon to 
be Doctrine (maybe?) implementation, Symfony would probably go quite a 
bit faster.

Also note that they are still not at 1.0, and their API changes and they 
aren't even expected to maintain much backward compat. at this point.  
Adopting it in a critical environment is probably not a good idea, at 
least not until they hit 1.0 and start making promises about maintaining 
as much BC as possible, etc..

On a positive note, their code is incredibly clean, documented, and elegant.

HTH,

Rick



Ajai Khattri wrote:
> Daniel Krook wrote:
>   
>> I'm evaluating CodeIgniter for a brand new project.   It seems to be a 
>> fairly new MVC framework and came recommended by some coworkers.   It 
>> seems to position itself directly against CakePHP and model itself on 
>> Rails.   Can anyone give a thumbs up or down?
>>     
>
> I have a colleague who also chose to check out CodeIgniter - what are 
> your impressions of it?
>
> I would also like to know if anyone is using any of these frameworks in 
> a large-scale and/or high-traffic web site? Was your framework of choice 
> easy to scale? Any used more than one framework and make a few comparisons?
>
> I may have an opportunity to work on a major web site (porting their 
> existing application from Perl to PHP) and Im told they are very much 
> into "frameworks" so now Im wondering if anyone has some empirical 
> analysis of the strengths and weaknesses when applied to large web sites?
>
>
> Funny: back in the 90s I was porting C applications to perl... ;-)
>
>
>