Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

sigzero (5768)

  (email not shown publicly)

I am the proverbial "accidental" programmer. I have found that I really like Perl and programming so I am pursuing that route now. I am the Debian systems administrator and junior Perl programmer for a company called Inspire.

Journal of sigzero (5768)

Friday September 05, 2008
07:52 PM

A short talk with a Java developer

[ #37367 ]

I will start this off by saying I like and respect this person as a Java developer.

[me] $coworker is having problems with the CLASSPATH on the command line.
[dev] I don't know how to do that either.
[me] Really?
[dev] eclipse takes care of that for me and I haven't had to do that in years.
[me] Mmmm...uh...okay.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • I think this short talk explains so many things about the "parallel universes" or "camps" if you like (Perl, Java, ...) where developers actually live. :)
  • Yup. At $work I've joined a Java project a few months back, and that total reliance on Eclipse to take care of all the under-the-hood details (and the ensuing side-effect that no-one really know how to tinker an ant file, or compile from the command-line) is something that bemuse me to no end.

    But then, this could also be a defense mechanism. When I finally found a way for eclipse to show me the classpath used for the project, I must say that a little part of me died. Ye gods was it ever prolix...

  • Actually, this sounds like a success to me! A high-level tool that is so successful that you don't need to read the specs for the low-level tool? That's a successful abstraction.

    • You have a different definition of "success" that I do.

      • By success, in this case I meant that someone did not need to learn something that was not relevant to getting his/her work done. Of what benefit is knowing the classpath syntax for command-line Java? Analogy: using Perl makes knowing the order of arguments of the malloc function useless. Automatic memory management is a success for Perl, like automatic project management is a success for Eclipse.

        For reference, that classpath syntax is actually simple, but platform-specific (colon or semi-colon as path s

        • that level sure. But you are taking it to the tool level which is where your Perl analogy falls apart. eclipse is not Java and "I" would think a Java programmer would know the classpath syntax.

          • You only see the difference because the Perl project-management tools aren't good enough yet.

            We'll be fixing that.