Posted by Andy Jeffries on 05/05/06 10:55

On Thu, 04 May 2006 16:29:17 -0700, Chung Leong wrote:
>> When the stakes are "high" (which is a relative term from business to
>> business) then the consultant should recommend the best solution.
>
> And the best solution in that case is one that has the lowest risk. Using
> PHP in a system that's mission critical for your business is a high risk
> proposition--both from a objective and selfish, save-my-own-ass
> perspective. For one thing, there are no patches for PHP. To plug a hole
> or fix a bug you have to do a point upgrade.

Or change the source yourself using a diff from the source code. If
you're a big development company then it's not much effort to do that on
one server then roll it out to the others through your choice of
distribution/packaging method.

The bonus is *YOU CAN DO THAT*, with MS you're stuck in to waiting for
their release cycle after they've tested that it works on Chinese Windows
with a Russian language editor running Office 97 (even though the patch to
the ASP component isn't at all related, they have to test it to ensure the
entire experience isn't broken).

Cheers,


Andy

--
Andy Jeffries MBCS CITP ZCE | gPHPEdit Lead Developer
http://www.gphpedit.org | PHP editor for Gnome 2
http://www.andyjeffries.co.uk | Personal site and photos

[Back to original message]