Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • <rant>So if I wrote a poorly informed diatribe about how perl sucks so much because I can't use it for my medical imaging needs*, would it be equally valid? Why is it so awful when people spout FUD and nonsense about perl but it's fine when it's about other languages?</rant>

    What's funny is I wind up saying the same thing to Java people about Perl :-)

    (*It could be great for my hypothetical medical imaging needs, but that's beside the point.)

    • So if I wrote a poorly informed diatribe about how perl sucks so much because I can't use it for my medical imaging needs*, would it be equally valid?

      I think that analogy would only hold true if the company that manufactured the medical imaging equipment also wrote and owned Perl - then forced you to use Perl. I probably should have said "totally valid for solaris users" in my OP, though.

      What we have in the case of Sun/Java/Solaris is a company that owns the platform and thus owns the sysadmin tools on

      • So now they're replacing old, but quick and stable tools like admintool with slow, bloated (but pretty) Java programs like Sun Management Console.
        Well, that's just dumb. :-) Doesn't Sun have enough to worry about without rewriting major pieces of software their core constituency depends on? Not only is it violating the "don't fix it if it ain't broke" law, it's introducting change to sysadmins who IME tend to be a group who doesn't respond well to change. With good reason: change frequently comes at the expense of stability and predictability.