They all seemed to think that JAVA (insert silence) was God, and superior to all languages. Their main point was that java only spawned one process and could handle hundreds of users and that perl, on the other hand, could not.

Eh, this was a Unix Fundamentals class, wasn't? I've given Unix Fundamentals classes, and what we do it stuff like browsing the file system, looking at files, editing them, commands like cd, ls, more, cat, vi, grep, find. We talk about in/output redirection, pipes, exit status, awk, sed. A natural environment for perl.

What's the deal about processes? If I start a perl program, I start a single process. If I start a Java program, I start a single process. Now, they may claim a perl process is taking lots of memory, but so is your typical Java program. What they mean by "a Java program could handle hundreds of users" is beyond me. You aren't writing operating systems in your Unix Fundamentals class, I hope?

In my professional opinion, I find that Java *doesn't* scale. It's wasting too much memory - many applications come with their own Java run-time enviroment (because the "write once, run everywhere is a blatant lie"), and a handful of Java run-time environments quickly consume all the memory available, even if it's 2 Gb. Now, Perl doesn't scale well either, it's also memory hungry. With Perl it isn't so much the run-time environment (although that still isn't memory friendly), but the amount of memory data takes.

Mind me, I'm not saying Java is a bad language. It certainly does have its merits. It's syntax isn't complex, and not as rich as Perls. It has strong typing, and for a lot of programmers, Java is a better language than Perl. It keeps you further away from the idiosyncrasies of Unix. This is sometimes a good thing - but try to make a Java program that pays attention to environment variables. If I have to choose between Java and Perl, I can make that decision based on many criteria. For some criteria, Perl will win. For some, Java will win. But scalability isn't a criterium for which Java will be a clear winner (they both lose ;-)).

If something really has to scale, with all other things equal, C is the only logical choice.

Abigail

In reply to Re: Is perl scalable? by Abigail-II
in thread Is perl scalable? by silent11

Title:
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!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • 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, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            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.