NYCPHP Meetup

[Baer, Jon]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I have a question on how others are handling their 3rd party frameworks
... Specifically the ones under some type of version control (and when
your code itself is under version control).  There was a recent security
fix for CakePHP and an ~svn up~ provided the quickest way to get to the
fix*.  

The problem w/ this is that there are potentials for breakage under your
unit tests (or just your code if you don't do test cases).  If you have
a lot of code between the revisions of your last framework update it can
be cumbersome to check everything.  

Would tagging your code based on major framework updates (1.x.x.x) be
the best solution in case something goes awry?

Im also thinking of symlinking across the framework versions as another
alternative ... Just wondering how others might be handling it ...

- - Jon

*On a side note Ive heard of mixed effects of using svn:externals
(albeit an svn upgrade, etc) and still not sure if it is the best
option.

- -----Original Message-----
From: talk-bounces at lists.nyphp.org [mailto:talk-bounces at lists.nyphp.org]
On Behalf Of Rick Olson
Sent: Thursday, September 14, 2006 9:03 PM
To: NYPHP Talk
Subject: Re: [nycphp-talk] Cake v. Symfony [CodeIgniter?]

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... ;-)
>
>
>   

_______________________________________________
New York PHP Community Talk Mailing List
http://lists.nyphp.org/mailman/listinfo/talk

NYPHPCon 2006 Presentations Online
http://www.nyphpcon.com

Show Your Participation in New York PHP
http://www.nyphp.org/show_participation.php
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (MingW32)

iD8DBQFFDsFe99e5DI8C/rsRAuEPAKC0vEgTQoYC1J4DwSJyk0fKJwkEcACg2B5n
LFkaSuy977jn0E9w54Emgbs=
=zsam
-----END PGP SIGNATURE-----