NB: This is all in response to a few of FoxtrotUniform's statements with respect to Lisp. I may be making a mountain out of an anthill, you've been warned.
I like Perl and I like Lisp, but I like them both for the same reason: they adapt to me and my problem domain. If I want to write structured code I can, if I want to write OO I can, if I want to build an unmaintainable goto hell I can.
Lisp (in the form know as Common Lisp) is just as much about solving real problems as Perl is and it's about using the best tools available, be they libs or paradigms, just like Perl. When OO became the Big Thing it was added to Lisp (CLOS). When the next Big Thing comes along (Aspect Oriented Programming? CLP? distributed programming?) you'll find a CPAN module for it and a Lisp package for it. It's the ability to adapt to the programmer and the problem (aka TIMTOWTDI) which Paul Graham likes so much in Lisp.
Love Perl, make Perl the greatest, fight for Total Perl Domination, but don't think you're special.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
