losing many of those 'nasty features' that confounded so many programmers, Pointers, malloc/free, system calls,

Why would I want to manage memory myself? To me, that's just one more tedious job that the computer should be doing for me. While I've occationally had problems with garbage collection (usually a poorly-coded DESTROY subroutine), they've almost always turned out to be my fault.

System calls are just something you have to live with sometime, and I have run into Java's poor support for them on more than one occation. Saying its "unportable" is silly. If the given system anything close to POSIX, they should work. If it's not close to POSIX, you'd have a hard time finding a Java VM for it anyway.

I won't comment on pointers, since I haven't done enough C programming to get myself buried in them.

Perl was marketted to the community at large with not much more than, "use this, see if you like it."

Zelotry trancends languages. I don't think the Perl community gets off the hook here. Perl just doesn't have a multi-billion dollar corporation with a marketing department to match.

Ever meet a hard core Perl programmer who didn't know anything more than Perl?

No, but I've met plenty of PERL programmers who didn't :)

Ever meet a Java programmer who knew anything more than Java,and many times not even that much?

Yeah, me. I used to do everything in Java, until I got sick of its bloated API. I had learned BASIC, a little Perl, and C/C++ before hand.

Java the Language: beautiful, clean, nearly-pure-OO
Java the API: which ear did my brain crawl out of?

I have a love-hate relationship with Perl OO. No implicit passing of $self, no (true) function prototyping, having to bless your reference on your own, and generally placing more of the burden on the programmer. At the same time, I realize that many of these things allow for increadibly powerful things to be done that simply can't be done in Java, or would take an increadible ammount of lines to do.

----
I wanted to explore how Perl's closures can be manipulated, and ended up creating an object system by accident.
-- Schemer

:(){ :|:&};:

Note: All code is untested, unless otherwise stated

In reply to Re: Hype Vs Substance (Yet Another Perl Versus Java Node) by hardburn
in thread Hype Vs Substance (Yet Another Perl Versus Java Node) by ptkdb

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.