<br><font size=2 face="sans-serif">PHP (as well as most RAD languages) gives quick gratification (i.e. results). This is a strength, but I would argue that it is an even greater weakness.</font>
<br>
<br><font size=2 face="sans-serif">As I mentioned, too often are people eager to get "results" without properly planning. As the system grows, it becomes harder and harder to add functionality (osCommerce is a *fantastic* example of this).</font>
<br>
<br><font size=2 face="sans-serif">It *tends* to be that the PHP advocates pump the "instant results" where as the detractors push the lack of design in most PHP solutions. Where you stand typically depends on whether you are in the project for the "long haul" or not. With the right forethought and coding practices, heck even Visual Basic can be a worthy tool. But as in all things, it is a "right tool for the job" situation...</font>
<br>
<br><font size=2 face="sans-serif">If people think of Perl as "a dirty scripting language", they'll never fully appreciate its incredible strength and flexibility (just take a look at any of the stuff Damian showed off last week at YAPC...absolutely mind blowing...sufficiently close to Magic!)</font>
<br>
<br><font size=2 face="sans-serif">If people think of PHP as a "poor Perl", then they likely aren't looking at "just get a website up" type projects. (However, to those people's defense, they may understand the principle that every line of code written must be supported for 50+ years...which it must).</font>
<br><font size=2 face="sans-serif"><br>
greg.fenton<br>
----<br>
Greg Fenton<br>
Consultant, Solution Services<br>
iAnywhere Solutions</font>