Slashdot Mirror
Is Apache 2.0 Worth the Switch for PHP?
An anonymous reader writes "It seems like some of the members of the Apache Software Foundation are a little angry with the PHP Community because they don't recommend using Apache 2.0 with PHP. Since PHP is installed on half of all Apache servers this is a major issue for them. A number of high-profile PHP community members such as John Coggeshall and Chris Shiflett have blogged about this decision in light of a recent posting by Apache Software Foundation Member Rich Bowen which called PHP's anti-Apache2 stance FUD. Is there any real reason for the PHP community to start recommending Apache 2.0, especially when the 1.3.x series of Apache is rock solid and proven? Note Rich did later commend PHP for being a great product, so it's not all flames."
...and start using mod_python which will only work on apache 2.
That's because Perl is dead. Thus, mod_perl isn't newsworthy.
...then why not switch to a far superior platform like ASP.NET on IIS6?
Who can specifically give me a reason to switch from A1 to A2 if I'm using PHP?...For the record, I'm still using Win2k and Office97...
You wouldn't understand.
I would love to see them get rid of the PHP license. BSD (and hence viral) with an "URL trapdoor" .. no thanks.. I prefer my licenses to be all contained within the text of the license, not pointing to arbitrary urls.
It seems the PHP folks are spreading FUD. But what would you expect from the troglodyte designers of a bottom feeding language like PHP? There are many technically better alternatives, like Apache mod_scheme. Why not use them instead?
an ill wind that blows no good