[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[no subject]
- <!--x-content-type: text/plain -->
- <!--x-date: Wed Feb 11 08:55:16 2004 -->
- <!--x-from-r13: syrgpu ng culqrnhk.bet (Tyrgpu) -->
- <!--x-message-id: [email protected] -->
- <!--x-reference: [email protected] -->
- <!--x-reference: [email protected] -->
- <!--x-reference: [email protected] -->
- <!--x-reference: 200209251519.40552.scherrey@proteus-tech.com -->
- <!--x-reference: [email protected] -->
- <!--x-reference: 1076463870.19456.7.camel@hideaway --> "http://www.w3.org/TR/html4/loose.dtd">
- <!--x-subject: [ale] Re: Python web programming -->
- <li><em>date</em>: Wed Feb 11 08:55:16 2004</li>
- <li><em>from</em>: fletch at phydeaux.org (Fletch)</li>
- <li><em>in-reply-to</em>: <1076463870.19456.7.camel@hideaway> (John Wells's message of "10 Feb 2004 20:44:31 -0500")</li>
- <li><em>references</em>: <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <1076463870.19456.7.camel@hideaway></li>
- <li><em>subject</em>: [ale] Re: Python web programming</li>
<a rel="nofollow" href="http://www.ukuug.org/events/linux2002/papers/html/php/index.html">http://www.ukuug.org/events/linux2002/papers/html/php/index.html</a>
>From the conclusion:
For more experienced developers, though, the language's
simplicity rapidly turns into complexity, slowing down the
development process. These developers are the ones who have the
skills needed to build large and/or complex websites; using PHP
for such sites therefore tends to be a net loss. This tendency
is reinforced by PHP's lack of the linguistic features needed to
promote working on large software projects. If your project is
at all large or complex, it may be better to look elsewhere when
choosing an implementation language.
Personally, I'd go with either HTML::Mason (<a rel="nofollow" href="http://masonhq.com/">http://masonhq.com/</a>) or
Template Toolkit (<a rel="nofollow" href="http://template-toolkit.org/">http://template-toolkit.org/</a>). ORA has books on
both (although I've yet to pick up the TT one; the Mason one is
available online at <a rel="nofollow" href="http://masonbook.com/">http://masonbook.com/</a> and the dead tree version is
handy). Mason is a bit more PHP-y in that you can wind up tying your
code and presentation together fairly tightly, while TT tends to lend
itself more to a tiered approach with code seperate and hidden from
the presentation side (not that you can't do either style in either
one, just the way they happen to work). Personally I use Mason for
web stuff since it's closer to straight perl, but I've almost
forgotten how to write m4 since learning TT and tend to use it
anywhere I need templating in a non-web context.
If you're set on Python, definately look into Zope (and you have my
condolences :).
--
Fletch | "If you find my answers frightening, __`'/|
fletch at phydeaux.org | Vincent, you should cease askin' \ o.O'
| scary questions." -- Jules =(___)=
| U
</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00361" href="msg00361.html">Python web programming (was Re: [ale] C#)</a></strong>
<ul><li><em>From:</em> jb at devsea.com (John Wells)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00368.html">[ale] SuSe and Scrollwheel</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00370.html">[ale] SuSe and Scrollwheel</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00364.html">Python web programming (was Re: [ale] C#)</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00362.html">[ale] OT: outsourcing call centers</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00369"><strong>Date</strong></a></li>
<li><a href="threads.html#00369"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>
<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>