The first thing to note is that our working definition of intuitive here translates to: based on prior knowledge.
PHP is a tag based language and places relatively complex functions at the fingertips of your average joe newbie. It is therefore more intuitive and remarkably faster to develop with when you are employing a pool of bell-curve skilled programmers. It is for this same reason that we offer cold fusion for the dynamic sites we host: if you have a bit of experience with HTML, a one day class in cold fusion lets you work with cookies and databases, et cetera. In our evaluation of what to support in terms of web application languages, we selected perl for its power and Cold Fusion for its speed of deployment; the latter over PHP because of its maturity { security, stability, features, IDE support }. I laugh at the Java bashing because as time wore on, you guessed it, we were asked to write an enterprise calendar in Java. Derrick Stone Internet Specialist Web Development Center UVa Health System ICQ# 1464194 -----Original Message----- From: Richard Clarke [mailto:ric@;likewhoa.com] Sent: Wednesday, October 30, 2002 11:34 AM To: [EMAIL PROTECTED] Subject: [OT] Re: Yahoo is moving to PHP ?? List, You are probably not the best people to ask for an answer which might advocate PHP, but..... Can someone who is more proficient in PHP than I (I have used it for 5 minutes) explain to me why it is quicker to prototype things in PHP? I can't understand this statement. Surely this is only applicable to people who are not proficient with mod_perl & [% my_templating_engine %]? Much of the code from PHP based websites which I have read has seemed to take this prototyping idea too much to heart. It looks more like an overly complex prototype than a well working application. /me doesn't get it.