Comments on: Why I Don’t Want To Use Tools Written For PHP 4 http://www.littlehart.net/atthekeyboard/2009/11/09/why-i-dont-want-to-use-tools-written-for-php-4/?utm_source=rss&utm_medium=rss&utm_campaign=rss Facebook should've be written in unicornSchemaLang, because everyone *knows* that PHP is no good for anything, right? Fri, 30 Jul 2010 05:30:02 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Chris Hartjes http://www.littlehart.net/atthekeyboard/2009/11/09/why-i-dont-want-to-use-tools-written-for-php-4/comment-page-1/#comment-14821 Chris Hartjes Wed, 11 Nov 2009 00:22:01 +0000 http://www.littlehart.net/atthekeyboard/?p=577#comment-14821 @Adam I pick on CodeIgniter because I use it every day at work. Familiarity breeds contempt, and all that. :) You're absolutely right about CakePHP too. CakePHP probably has even more code in it that checks for PHP 4, and that is the main reason why I could not recommend that we use it for future projects at work. Zend Framework started all this off by insisting that it be PHP 5+ only, and now that Symfony has decided that the next major release will be PHP 5.3 only, I think the time has come to embrace the idea that the amount of work required to preserve backwards compatibility with PHP 4 is a waste of time given how long PHP 5 has been available. @Adam

I pick on CodeIgniter because I use it every day at work. Familiarity breeds contempt, and all that. :)

You’re absolutely right about CakePHP too. CakePHP probably has even more code in it that checks for PHP 4, and that is the main reason why I could not recommend that we use it for future projects at work.

Zend Framework started all this off by insisting that it be PHP 5+ only, and now that Symfony has decided that the next major release will be PHP 5.3 only, I think the time has come to embrace the idea that the amount of work required to preserve backwards compatibility with PHP 4 is a waste of time given how long PHP 5 has been available.

]]> By: Adam http://www.littlehart.net/atthekeyboard/2009/11/09/why-i-dont-want-to-use-tools-written-for-php-4/comment-page-1/#comment-14820 Adam Tue, 10 Nov 2009 22:36:52 +0000 http://www.littlehart.net/atthekeyboard/?p=577#comment-14820 Say now!!! Codeignitor, your least favorite framework, suffers from the same issues that a framework you once wrote a lot about: Cakephp. I'm an avid baker, but I do think its too late to just now be working on a php5 only version. And that version surely won't be out this year. Anyways, the point of my post was: why only pick on CI? Why not Cake as well? Say now!!! Codeignitor, your least favorite framework, suffers from the same issues that a framework you once wrote a lot about: Cakephp. I’m an avid baker, but I do think its too late to just now be working on a php5 only version. And that version surely won’t be out this year. Anyways, the point of my post was: why only pick on CI? Why not Cake as well?

]]> By: Brendon Kozlowski http://www.littlehart.net/atthekeyboard/2009/11/09/why-i-dont-want-to-use-tools-written-for-php-4/comment-page-1/#comment-14819 Brendon Kozlowski Tue, 10 Nov 2009 16:12:07 +0000 http://www.littlehart.net/atthekeyboard/?p=577#comment-14819 PHP suffers from its own popularity. It's as simple as that. Many people find, are given, or are suggested web-apps that were built with a specific version - these people are not necessarily 100% computer literate and when something breaks, they blame their hosting provider. Hosting providers don't want to deal with the outcry from it, and therefore hold on to the older versions of PHP as long as they can, while still offering newer versions (if their server's setup properly) to those that opt-in. PHPRC and strives in the newer PHP versions for user-specific ini settings should alleviate a lot of that in the future. Before PHP became popular, the same problem existed with Perl. ...and, sorry, you were asking how Ruby (RoR) and Python (Django) handle that and I really have no idea. PHP suffers from its own popularity. It’s as simple as that. Many people find, are given, or are suggested web-apps that were built with a specific version – these people are not necessarily 100% computer literate and when something breaks, they blame their hosting provider. Hosting providers don’t want to deal with the outcry from it, and therefore hold on to the older versions of PHP as long as they can, while still offering newer versions (if their server’s setup properly) to those that opt-in. PHPRC and strives in the newer PHP versions for user-specific ini settings should alleviate a lot of that in the future.

Before PHP became popular, the same problem existed with Perl. …and, sorry, you were asking how Ruby (RoR) and Python (Django) handle that and I really have no idea.

]]> By: Walker Hamilton http://www.littlehart.net/atthekeyboard/2009/11/09/why-i-dont-want-to-use-tools-written-for-php-4/comment-page-1/#comment-14812 Walker Hamilton Mon, 09 Nov 2009 22:33:30 +0000 http://www.littlehart.net/atthekeyboard/?p=577#comment-14812 Q: Is PHP the only programming language for the web where the people running older versions hold onto it kicking and screaming, despite gobs of evidence that newer stable versions of the language have fixed bugs, perform better, and offer new useful features? A: Yes. Q: Is PHP the only programming language for the web where the people running older versions hold onto it kicking and screaming, despite gobs of evidence that newer stable versions of the language have fixed bugs, perform better, and offer new useful features?

A: Yes.

]]>