Also, think of down the road; 1.2 apps currently being developed will at some point "feel" like 1.1 apps that are being developed right now, as the new bleeding edge cake will probably be 2.x... "Legacy Support" or "backwards-compatibility" or whatever term you choose to use, is without a doubt huge and very significant. From another perspective, there's another reason why a lot of web hosts still offer 4 that maybe wasn't mentioned here: app support. A lot of people have big apps written in php4 that are not easily moved to 5 and won't go with a web host that doesn't support 4. I get the notion of "moving forward", but I think the point Nate, Felix and others are trying to make is that supporting php 4 is not "stunting" CakePHP's ability to perform, or to be scalable, or whatever....
On May 29, 3:22 am, Felix Geisendörfer <[EMAIL PROTECTED]> wrote: > > That guy needs PHP4, this host needs PHP4, but no one is saying > > that I need a PHP4 support. This is the same scenario happened when > > PHP4 is released. It's always better to move upwards whether it's PHP > > or CakePHP (how many people are going to stick to 1.1 for instance?) > > You *really* need to listen to the other folks. I'm working on one of > the biggest cake apps around (300db tables, ~70 controllers, etc.). And > guess what? It's 1.1. The reason for this is that the project was > started about ~6 month ago when 1.2 was not where it's now and the team > decided it would not be worth to the pain to constantly stay in sync > with HEAD and deal with early adopter issues. And now guess further. > This application won't magically convert itself to 1.2 and that is not > because we don't want it to, but because we'll have to refactor > thousands and thousand lines of code done in ~5000 svn commits. So yes, > people will stick to CakePHP 1.1, PHP4 (the project I mentioned is php5) > and other old technologies and will highly appreciate any support going > into them. Now of course when you are starting a new project and it's > not all that big I'm somebody who also favors the usage of cutting edge > technology. But get real, for a really big app you need to rely on > technologies that are somewhat proven to work depending on the > environment you are working in. Of course, as a startup made up of a > couple guys living on Pizza, Coke and Hope you can make the craziest > choices and go with a Lisp-Haskell-HomebrewDB-Hybrid application or > whatever. That's because you'll either fail or be lucky enough to > discover a powerful combination that exceeds your wildest expectations. > But please give the rest of a world a brief moment to catch up with you > and don't make their life harder then necessary by promoting a no-legacy > support doctrine. > > Thanks a lot, Felix > --------------------------http://www.thinkingphp.orghttp://www.fg-webdesign.de > > R. Rajesh Jeba Anbiah wrote: > > > On May 29, 11:22 am, haj <[EMAIL PROTECTED]> wrote: > > >> PHP4 support is one of the most important features and advantages and > >> selling point of cakePHP. > > > That guy needs PHP4, this host needs PHP4, but no one is saying > > that I need a PHP4 support. This is the same scenario happened when > > PHP4 is released. It's always better to move upwards whether it's PHP > > or CakePHP (how many people are going to stick to 1.1 for instance?) > > >> This is not for some CS student's research > >> homework. Work in the field and realise a significance of PHP4 > >> support. > > > Ok. > > > -- > > <?php echo 'Just another PHP saint'; ?> > > Email: rrjanbiah-at-Y!com Blog:http://rajeshanbiah.blogspot.com/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
