Comments on: Disruptive Technology http://www.sitepoint.com/blogs/2004/04/26/disruptive-technology/ News, opinion, and fresh thinking for web developers and designers. The official podcast of sitepoint.com. Fri, 05 Dec 2008 02:42:54 +0000 http://wordpress.org/?v=2.5 By: Richard Cyganiak http://www.sitepoint.com/blogs/2004/04/26/disruptive-technology/#comment-242 Richard Cyganiak Wed, 31 Dec 1969 19:00:00 +0000 793264837#comment-242 <p>PHP's #1 feature is cheap hosting.</p> <p>I'm a student. I know some PHP and some Java. I have to use Java for university projects. But all the web stuff I do in my free time for fun, the stuff I really care about, is done in PHP. Simply because I don't know where to get Java hosting for $10 a month. For the same reason I didn't even bother to look at .net.</p> <p>And in the future, I'm probably going to use PHP for any project where I can get away with it, simply because I know it so well.</p> <p>Back to my J2EE coursework :-/</p> PHP’s #1 feature is cheap hosting.

I’m a student. I know some PHP and some Java. I have to use Java for university projects. But all the web stuff I do in my free time for fun, the stuff I really care about, is done in PHP. Simply because I don’t know where to get Java hosting for $10 a month. For the same reason I didn’t even bother to look at .net.

And in the future, I’m probably going to use PHP for any project where I can get away with it, simply because I know it so well.

Back to my J2EE coursework :-/

]]> By: Anonymous http://www.sitepoint.com/blogs/2004/04/26/disruptive-technology/#comment-243 Anonymous Wed, 31 Dec 1969 19:00:00 +0000 793264837#comment-243 <p>saying that php is #1 for ease of use is being *very* short sighted. <br /> this may be true just if you consider that there is just one other opponent, J2EE.</p> <p>Perl,python and ruby can all be embedded in html, if you wish. </p> <p>The reason php is succesfull is that it was the first, not the best. </p> saying that php is #1 for ease of use is being *very* short sighted.
this may be true just if you consider that there is just one other opponent, J2EE.

Perl,python and ruby can all be embedded in html, if you wish.

The reason php is succesfull is that it was the first, not the best.

]]> By: HarryF http://www.sitepoint.com/blogs/2004/04/26/disruptive-technology/#comment-244 HarryF Wed, 31 Dec 1969 19:00:00 +0000 793264837#comment-244 <p><blockquote><p><br /> Perl,python and ruby can all be embedded in html, if you wish.<br /> </p></blockquote></p> <p>I've never looked at what Ruby can do web-wise but while it's true both Perl and Python have means for "HTML preprocessing" (embedded in HTML), when it comes to ease of use PHP still has the edge from where I stand.</p> <p>Perl suffers from it's syntax (subjective point I know) while setting up mod_perl + an HTML preprocessor (which one?) is not trivial compared to a PHP install.</p> <p>Python is a great language but has only <i>just</i> got an HTML preprocessor everyone can agree on (<a href="http://www.sitepoint.com/blog-post-view.php?id=155823">blogged here</a>). In principle Python is now easier to use than PHP but in practice this platform still needs to be "discovered". There's also issues like Python being strongly typed and it's DB API being a little too generalistic for web apps right now. Otherwise, if you check out some of the responses to what people were saying in <a href="http://www.sitepoint.com/blog-post-view.php?id=155091">How do you learn how to use a library?</a>, the main source was online articles. You stuggle to find any web related subject that someone <i>hasn't</i> published their thoughts on in PHP.</p> <p>Note I'm not arguing that an HTML preprocessor is the best solution from a software design point of view but just that it makes life very easy in the short term, and that attracts users.</p> <p><blockquote><p><br /> The reason php is succesfull is that it was the first, not the best.<br /> </p></blockquote></p> <p>That's very true. But I think there's more to it than that - the <a href="http://www.sitepoint.com/forums/showpost.php?p=1121502&postcount=2">worse is better</a> notion. PHP was in the right place at the right time and doing the right things. But if it had, for example, imposed Java-like rigours on the programmer, it wouldn't have been popular. There's an interesting take on the history of PHP <a href="http://www.trachtenberg.com/PHP.pdf">here</a> (PDF) which considers where Perl was at the time PHP started.</p>

Perl,python and ruby can all be embedded in html, if you wish.

I’ve never looked at what Ruby can do web-wise but while it’s true both Perl and Python have means for “HTML preprocessing” (embedded in HTML), when it comes to ease of use PHP still has the edge from where I stand.

Perl suffers from it’s syntax (subjective point I know) while setting up mod_perl + an HTML preprocessor (which one?) is not trivial compared to a PHP install.

Python is a great language but has only just got an HTML preprocessor everyone can agree on (blogged here). In principle Python is now easier to use than PHP but in practice this platform still needs to be “discovered”. There’s also issues like Python being strongly typed and it’s DB API being a little too generalistic for web apps right now. Otherwise, if you check out some of the responses to what people were saying in How do you learn how to use a library?, the main source was online articles. You stuggle to find any web related subject that someone hasn’t published their thoughts on in PHP.

Note I’m not arguing that an HTML preprocessor is the best solution from a software design point of view but just that it makes life very easy in the short term, and that attracts users.

The reason php is succesfull is that it was the first, not the best.

That’s very true. But I think there’s more to it than that - the worse is better notion. PHP was in the right place at the right time and doing the right things. But if it had, for example, imposed Java-like rigours on the programmer, it wouldn’t have been popular. There’s an interesting take on the history of PHP here (PDF) which considers where Perl was at the time PHP started.

]]>