I think that this move will not bring the intended effect on Google's bottom line. The core user that is affected by this change is the enthusiast, setting up a custom domain for email for their family, opensource project, etc. This enthusiast user was advocating the Google services. I count myself as one such user whose recommendations has led at least 3 new small business customers for Google. Also their decisions to use Android over the competing platforms.
Now Google loses all of that. And since it is highly unlikely that they will discontinue their free Gmail, Calendar, Drive offerings the end of free custom domain accounts is unlikely to save them any money on hosting and will represent a net loss to them in the long run.
Roadsend is a development house unrelated to the PHP development team. I doubt that their compiler would make any noticable impact since they don't support many of the PHP's most useful extensions. I have not tested it but it looks to me that the people that would be interested in this are those that want to close source their own PHP code so I guess its only fair to pay for it.
Many useful PHP tools are open source. From the bytecode compiles such as APC and MMCache, debuggers (APD and XDebug).
I see tha fact that there are some companies out there providing commercial tools for PHP developers as a good thing(tm).
We're using PHP to connect to different sort of backend databases and other services. We used mostly Oracle in the past, but have made a move to Postgres mostly due to the cost. We're still using Oracle for clients who are willing to pay for it.
My most recent assignment was using DB2 on an IBM iSeries machine (formerly known as AS/400).
PHP can and is used to develop "enterprise" size web applications. It doesn't have to be Java. And I can been the cost of any Java shop around here.
A voice of reason. It is refreshing to see a diffrent viewpoint in this time of Java craze.
In my own experience (and I work for a web development house) you can cut down time of development by factor 5-10 using a weakly typed scripting language such as PHP.
Re:Breaking MySQL support - what *sses
on
PHP 5 Beta 1
·
· Score: 3, Interesting
Its would mean breaking MySQL's GPL license if PHP bundled current version of MySQL client libraries.
This because FSF claims that Apache and PHP licenses are not GPL compatible, thus linking against those is not premitted. It does not help that MySQL AB has chosen to change their client library license from LGPL to GPL after release 4.0 of MySQL
Nothing to do with the PHP development team really.
You can find more details on this story over at MSNBC.
It includes Novell's threats of legal action:
"SCO's actions are disrupting business relations that might otherwise form at a critical time among partners around Linux technologies and are depriving these partners of important economic opportunities," Messman stated. "We hope you understand the potential significant legal liability SCO faces for the possible harm it is causing to countless customers, developers and other Linux community members. SCO's actions, if carried forward, will lead to the loss of sales and jobs, delayed projects, canceled financing and a balkanized Linux community."
Slashdot Mirror
I think that this move will not bring the intended effect on Google's bottom line. The core user that is affected by this change is the enthusiast, setting up a custom domain for email for their family, opensource project, etc. This enthusiast user was advocating the Google services. I count myself as one such user whose recommendations has led at least 3 new small business customers for Google. Also their decisions to use Android over the competing platforms.
Now Google loses all of that. And since it is highly unlikely that they will discontinue their free Gmail, Calendar, Drive offerings the end of free custom domain accounts is unlikely to save them any money on hosting and will represent a net loss to them in the long run.
Roadsend is a development house unrelated to the PHP development team. I doubt that their compiler would make any noticable impact since they don't support many of the PHP's most useful extensions. I have not tested it but it looks to me that the people that would be interested in this are those that want to close source their own PHP code so I guess its only fair to pay for it.
Many useful PHP tools are open source. From the bytecode compiles such as APC and MMCache, debuggers (APD and XDebug).
I see tha fact that there are some companies out there providing commercial tools for PHP developers as a good thing(tm).
Not really
We're using PHP to connect to different sort of backend databases and other services. We used mostly Oracle in the past, but have made a move to Postgres mostly due to the cost. We're still using Oracle for clients who are willing to pay for it.
My most recent assignment was using DB2 on an IBM iSeries machine (formerly known as AS/400).
PHP can and is used to develop "enterprise" size web applications. It doesn't have to be Java. And I can been the cost of any Java shop around here.
A voice of reason. It is refreshing to see a diffrent viewpoint in this time of Java craze. In my own experience (and I work for a web development house) you can cut down time of development by factor 5-10 using a weakly typed scripting language such as PHP.
Its would mean breaking MySQL's GPL license if PHP bundled current version of MySQL client libraries.
This because FSF claims that Apache and PHP licenses are not GPL compatible, thus linking against those is not premitted. It does not help that MySQL AB has chosen to change their client library license from LGPL to GPL after release 4.0 of MySQL
Nothing to do with the PHP development team really.
It seems that Novell now admits that it has transfered the Unix copyright to SCO according to this article.
They still claim to own the patents so the SCO case appears to be solely about the Unix copyrights.
You can find more details on this story over at MSNBC.
It includes Novell's threats of legal action:
"SCO's actions are disrupting business relations that might otherwise form at a critical time among partners around Linux technologies and are depriving these partners of important economic opportunities," Messman stated. "We hope you understand the potential significant legal liability SCO faces for the possible harm it is causing to countless customers, developers and other Linux community members. SCO's actions, if carried forward, will lead to the loss of sales and jobs, delayed projects, canceled financing and a balkanized Linux community."