[no subject]

On Thu, Mar 11, 2004 at 10:34:54AM -0500, Fletch wrote:
> 
> You might want to check out this paper.  I've quoted the conclusion
> paragraph below.  And I trust there's no confusion about what I'd
> sugguest instead of either of your sugguestions. :) (mod_perl
> underneath either HTML::Mason or Template Toolkit, of course)
> 
> 
> Experiences of Using PHP in Large Websites
&gt; <a  rel="nofollow" href="http://www.ukuug.org/events/linux2002/papers/html/php/";>http://www.ukuug.org/events/linux2002/papers/html/php/</a>
&gt; 
&gt; 
&gt; 7. Conclusions
&gt; 
&gt; PHP is a convenient language for rapidly prototyping simple dynamic
&gt; websites. We bsites thus built can in many cases be deployed
&gt; indefinitely, without spending t ime and money on refactoring code in
&gt; a different language. PHP's simplicity makes it a good language for
&gt; inexperienced programmers, such as those moving from a pure
&gt; page-design role to a site development one.
&gt; 
&gt; For more experienced developers, though, the language's simplicity
&gt; rapidly turns into complexity, slowing down the development
&gt; process. These developers are the ones who have the skills needed to
&gt; build large and/or complex websites; using PHP for such sites
&gt; therefore tends to be a net loss. This tendency is reinforced by PHP's
&gt; lack of the linguistic features needed to promote working on large
&gt; soft ware projects. If your project is at all large or complex, it may
&gt; be better to l ook elsewhere when choosing an implementation language.
&gt; 
&gt; In cases where PHP has been determined to be inappropriate, what
&gt; language should be used? There is considerable choice here; few
&gt; languages are as bad as PHP for doing serious development work. The
&gt; author and his colleagues have had good results with Perl, and
&gt; believe that languages such as C++, Java, and Python should serve
&gt; equally well.
&gt; 
&gt; _______________________________________________
&gt; Ale mailing list
&gt; Ale at ale.org
&gt; <a  rel="nofollow" href="http://www.ale.org/mailman/listinfo/ale";>http://www.ale.org/mailman/listinfo/ale</a>

-- 

I used to be interested in Windows NT, but the more I see of it the more it looks like traditional Windows with a stabler kernel. I don't find anything technically interesting there. In my opinion MS is a lot better at making money than it is at making good operating systems.  -- Linus Torvalds


</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<ul><li><strong>Follow-Ups</strong>:
<ul>
<li><strong><a name="00334" href="msg00334.html">[ale] J2EE vs PHP</a></strong>
<ul><li><em>From:</em> fletch at phydeaux.org (Fletch)</li></ul></li>
</ul></li></ul>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00316" href="msg00316.html">[ale] J2EE vs PHP</a></strong>
<ul><li><em>From:</em> cfowler at outpostsentinel.com (Christopher Fowler)</li></ul></li>
<li><strong><a name="00319" href="msg00319.html">[ale] J2EE vs PHP</a></strong>
<ul><li><em>From:</em> fletch at phydeaux.org (Fletch)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00321.html">[ale] dragging response times</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00323.html">[ale] J2EE vs PHP</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00319.html">[ale] J2EE vs PHP</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00334.html">[ale] J2EE vs PHP</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00322"><strong>Date</strong></a></li>
<li><a href="threads.html#00322"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>

<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>