Before you write FUD you should really check your facts. The Zend Engine is under a BSD-like license meaning that it's here to stay that way. And the PHP license you are quoting is old. Look at http://www.php.net/license/3_0.txt. I hope you trust urls to php.net
I completely agree with you. The FSF has produced some of the finest open-source software. I never said they didn't and I use gcc on a daily basis. The fact that I prefer a BSD-like over the GPL does not mean I don't appreciate other people's work. It's not a religion for me. Just a preference.
There is nothing I do more than talk and be in touch with PHP users. I can assure you that a huge amount of those users are using PHP at some point for commercial purposes, whether they are part of a company or they are doing some odd contracting jobs here and there.
Again I already replied to this but the license you are looking at is not the latest PHP license. You can get the latest version at http://www.php.net/license/3_0.txt
Please next time use the latest license and not some ancient license. Clause (6) for instance doesn't exist anymore because the Zend Engine today is under a BSD-like license, which pretty much means, do whatever you wish! You are definitely entitled to your opinion but you should at least base it on relevant facts.
What I meant was that PHP's users are happy to be able to use PHP in whatever way they wish for their business, not having to think too much about license limitations. I definitely didn't mean that you can't make a living creating applications and services ontop of GPL software.
The problem isn't the core of PHP, but the dozens of PHP extensions and third-party libraries they use. Even if a library claims thread-safety, it is not always so. Therefore, we (as in the PHP development team) recommend to use PHP with the pre-fork MPM of Apache 2 or with Apache 1.3.
It is not only a matter of Apache but also a matter of PHP. Currently it is not recommended to run PHP in multi-threaded web servers. The main problem isn't the core of PHP but the dozens of PHP extensions and third-party libraries which they use. You can never be sure those are really thread-safe. So even if you're using Apache 2, best to stick to pre-fork MPM. Anyway, there are other ways to tackle connection pooling and these solutions might appear at some stage.
No because ini_set() happens too late in the game (it needs to be set before the compiler kicks in). However, you can user per-directory httpd.conf settings or.htaccess
Yes I can confirm. We, as in Zend, are working with Sun on the JSR 223. The result will be a Sun reference implementation of the standard (based on PHP) which defines what the interface between PHP (and other scripting languages) and Java will look like.
You are right, but the technology comparison was far from accurate. For example, PHP on Windows supports COM and it can be extended by both COM and dlls. A more thorough technology comparison would be a bit more accurate, but in any case, not only do you have to do a technology comparison but also a TCO comparison and that's where PHP wins. Not because it's free but because the development time is so much faster than with ASP.
So how do you explain PHP's install base overtaking ASP according in April last year (according to Netcraft)? I'll tell you why: a) Most people feel more comfortable running their web sites on UNIX based systems. b) PHP is cross-platform which is a big advantage for companies who want to create off-the-shelf applications. c) It is much easier to find libraries on the Internet which will do exactly what you want.
I am sure there are some other reasons. I'm not a Microsoft basher but let's just say that PHP is doing pretty well for good reasons.
If you'd like to see what's new in PHP 5, we got some of the leading PHP developers to write about new extensions they developed. I also posted the first chapter of my PHP 5 book in that section which gives an overview of what's new in PHP 5. This book will be part of the Bruce Perens series of Prentice-Hall and will therefore be open-source and freely accessible to anyone.
One of our design goals for PHP 5, was to keep backwards compatibility as much as possible. Actually most PHP 4 sites run out of the box with PHP 5. If there are problems, there's a compatibility mode (configurable via php.ini) which makes the object-oriented model behave the same as in PHP 4. Bottom-line: Very few people will have problems doing the upgrade. Of course you should thoroughly test your site before upgrading.
Slashdot Mirror
Before you write FUD you should really check your facts. The Zend Engine is under a BSD-like license meaning that it's here to stay that way.
And the PHP license you are quoting is old. Look at http://www.php.net/license/3_0.txt. I hope you trust urls to php.net
Andi Gutmans
I completely agree with you. The FSF has produced some of the finest open-source software. I never said they didn't and I use gcc on a daily basis. The fact that I prefer a BSD-like over the GPL does not mean I don't appreciate other people's work. It's not a religion for me. Just a preference.
Hi,
There is nothing I do more than talk and be in touch with PHP users. I can assure you that a huge amount of those users are using PHP at some point for commercial purposes, whether they are part of a company or they are doing some odd contracting jobs here and there.
Again I already replied to this but the license you are looking at is not the latest PHP license. You can get the latest version at http://www.php.net/license/3_0.txt
Please next time use the latest license and not some ancient license. Clause (6) for instance doesn't exist anymore because the Zend Engine today is under a BSD-like license, which pretty much means, do whatever you wish!
You are definitely entitled to your opinion but you should at least base it on relevant facts.
Hi,
What I meant was that PHP's users are happy to be able to use PHP in whatever way they wish for their business, not having to think too much about license limitations. I definitely didn't mean that you can't make a living creating applications and services ontop of GPL software.
The problem isn't the core of PHP, but the dozens of PHP extensions and third-party libraries they use. Even if a library claims thread-safety, it is not always so. Therefore, we (as in the PHP development team) recommend to use PHP with the pre-fork MPM of Apache 2 or with Apache 1.3.
It is not only a matter of Apache but also a matter of PHP. Currently it is not recommended to run PHP in multi-threaded web servers. The main problem isn't the core of PHP but the dozens of PHP extensions and third-party libraries which they use. You can never be sure those are really thread-safe. So even if you're using Apache 2, best to stick to pre-fork MPM. Anyway, there are other ways to tackle connection pooling and these solutions might appear at some stage.
No because ini_set() happens too late in the game (it needs to be set before the compiler kicks in). However, you can user per-directory httpd.conf settings or .htaccess
Yes I can confirm. We, as in Zend, are working with Sun on the JSR 223. The result will be a Sun reference implementation of the standard (based on PHP) which defines what the interface between PHP (and other scripting languages) and Java will look like.
You are right, but the technology comparison was far from accurate. For example, PHP on Windows supports COM and it can be extended by both COM and dlls.
A more thorough technology comparison would be a bit more accurate, but in any case, not only do you have to do a technology comparison but also a TCO comparison and that's where PHP wins. Not because it's free but because the development time is so much faster than with ASP.
So how do you explain PHP's install base overtaking ASP according in April last year (according to Netcraft)?
I'll tell you why:
a) Most people feel more comfortable running their web sites on UNIX based systems.
b) PHP is cross-platform which is a big advantage for companies who want to create off-the-shelf applications.
c) It is much easier to find libraries on the Internet which will do exactly what you want.
I am sure there are some other reasons. I'm not a Microsoft basher but let's just say that PHP is doing pretty well for good reasons.
If you'd like to see what's new in PHP 5, we got some of the leading PHP developers to write about new extensions they developed.
I also posted the first chapter of my PHP 5 book in that section which gives an overview of what's new in PHP 5. This book will be part of the Bruce Perens series of Prentice-Hall and will therefore be open-source and freely accessible to anyone.
One of our design goals for PHP 5, was to keep backwards compatibility as much as possible. Actually most PHP 4 sites run out of the box with PHP 5. If there are problems, there's a compatibility mode (configurable via php.ini) which makes the object-oriented model behave the same as in PHP 4.
Bottom-line: Very few people will have problems doing the upgrade. Of course you should thoroughly test your site before upgrading.