| Article: |
The PHP Scalability Myth | |
| Subject: | maintainability is king | |
| Date: | 2003-10-17 16:45:36 | |
| From: | anonymous2 | |
|
"I need to reduce the term scalability to its core concern: performance"
|
||
Showing messages 1 through 2 of 2.
-
maintainability is king
2003-10-18 03:01:40 anonymous2 [View]
-
maintainability is king
2003-10-17 19:16:37 anonymous2 [View]
I'll save you some time. PHP really sucks for projects more than a few pages. I'll briefly explain. It is about as far from concepts like type-safe as it could be made. Cute syntactic tricks are much more important (at least on the day you code your first program). Why do the PHP language developers bother saying that they added a function to the language if they aren't going to unambiguously document the damn thing?? Because the PHP team is entrenched with a screw-safety mindset and mean-spirited arrogance. If they weren't coding PHP they'd be creating viruses and stealing credit cards so I suppose we should be thankful. Zend was hatched from the same cesspool -- bug-laden crapware and rampant dishonesty from all angles.
This is the truth and readers, you have been warned.



On the practical front, PHP doesn't have such a mature set of development tools and there's still a fair amount of work to do on encapsulating common architectural issues in some form of re-usable package - PEAR is getting there although there's still some lessons to learn in re-use (PEAR is closer to CPAN right now than a well integrated class library). PHP5 is also needed to make things like error handling more uniform.
On the philosophical front, there's a different school of thought coming from an eXtreme programming angle which argues that static, compile time type checks are merely a subset of unit testing and don't bring you much closer to a bug free application. Bruce Eckel makes the case in Strong Typing vs Strong Testing. For a PHP unit test framework (there's a few), try Simple Test.