|
|
Posted by Jerry Stuckle on 05/05/06 04:52
Chung Leong wrote:
> Andy Jeffries wrote:
>
>>Then I think you have a deep seated issue in that you need someone to
>>blame when things go wrong.
>
>
> Try telling that to your boss after your recommendation has costed the
> company half a mil :-)
>
>
>>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.
> Quality control is substandard, with debilitating regressions creeping
> into released versions. And when these bugs are discovered, barely any
> effort is made to inform the user base of their existence.
>
And I would trust PHP a lot farther than ASP.Net.
And Microsoft has never regressed anything? ROFLMAO! I can't count the number
of rewrites I've been involved in before switching AWAY from MS products.
As for Quality Control - yes, I wish MS would get some. Their software is crap.
The only thing they have going for them is they have snowed those who don't
know a damn thing about IT but have high positions in big companies.
>
>>For web applications 9 out of 10 times (if not more) PHP is the best
>>solution and I have no issue recommending it even though there's no one to
>>pin the blame on if it goes wrong.
>
>
> I don't disagree, but the tenth is the one that the OP is looking for.
>
I don't think it is the tenth in this case. I would have absolutely no problem
with a PHP solution.
>
>>Think of it this way, ask the customer "which would you prefer: a
>>platform with someone to blame when it all goes wrong or a platform that
>>actually works?"
>
>
> As a government employee, I say the former is preferable. LOL
>
Ah, that explains things. Governments have never been noted for making
intelligent decisions.
> But seriously, in all business decisions one has to weight the
> potential rewards against the risks involved. To say that a switch to
> PHP is good because so-and-so big-shot company is using it is as silly
> as to say the switch shouldn't be made because so-and-so isn't using it.
>
Yep. And there are way too many risks with MS products!
Sorry, Chung, you're in the wrong newsgroup if you want to bash PHP and extol
the virtues of MS products.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================
Navigation:
[Reply to this message]
|