Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer

Comment on

( #3333=superdoc: print w/ replies, xml ) Need Help??
You may have had a miserable experience with Lisp, but I think that you are writing it off far too easily. First of all a 500,000 line Java program is likely to be about a 50,000 line Lisp program. The factor of 10 difference in code size for the same task will pay for itself in maintainability. OK, since the lines will do more they will be harder to follow. Say a factor of 3. But that makes the overall code base about a factor of 3 easier to understand.

Of course just glancing at the code base what you first notice is that you have to think. As petral pointed out to me once, this is analagous to the division between readable and legible fonts. Legible fonts are ones which can be seen easily from a distance and under poor viewing conditions. A readable font is one which you can easily read large quantities of. They are not the same. Lisp is very definitely not legible. But it lends itself to readable code.

And it gets better. Your reduced code size makes it possible to work with a smaller team. Since intrateam communication has been known for decades to be the biggest bottleneck on large projects, that is an even bigger win. Therefore you have less code, your code base is easier to understand, and you have a smaller team that can work faster. Who would you bet on?

This isn't just theory. Read Paul Graham's article Beating The Averages about the history of ViaWeb. One of the many points that he made is that they found that any competitor who was advertising for Java programmers could just be written off. They simply weren't going to be serious competition...

(Many of the same points apply to Perl of course...)

In reply to Re (tilly) 2: Perl vs Lisp/Java/C/C++ by tilly
in thread Perl vs Lisp/Java/C/C++ by RhetTbull

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • Outside of code tags, you may need to use entities for some characters:
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.
  • Log In?

    What's my password?
    Create A New User
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others avoiding work at the Monastery: (9)
    As of 2015-03-04 12:53 GMT
    Find Nodes?
      Voting Booth?

      When putting a smiley right before a closing parenthesis, do you:

      Results (110 votes), past polls