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

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.
  • The war between PostgreSQL and MySQL continues to rage, which is disappointingly stupid--they should be trying to steal installations from Oracle, just as Perl and Python shouldn't be fighting with each other, they should be taking the battle to C++ and Java.

    The cause of the infighting is obvious. Everyone likes to think they've made the right choice, so everything else must automatically become the wrong choice. This is sad. Personally, I think Java is a fine language -- if you have the right problem

    • Personally, I think Java is a fine language -- if you have the right problem space. I once found myself in the position of recommending Java over Perl due to this, but have listened to people be absolutely astonished that I could even think such a thing.
      I say with no malice or sarcasm: I'd be fascinated to know what this problem space was.

      You are what you think.
      • by ziggy (25) on 2003.07.17 17:20 (#22207) Journal
        Just to echo Ovid's points above....

        I was talking about Perl with a hacker who is now managing a well-funded startup. Now that he's a Real Manager, he has to look at everything with conservative glasses.

        If he had a project in mind, had good Perl programmers available, and was reasonably confident that he could find more of them to extend/replace his team, then he'd spec out a project to use Perl. Yes, he'd pay more per programmer and they'd get done faster, but his primary goal is risk mitigation, not time to market or reduced costs. There's nothing worse than starting a project that has to be scuttled later because no one can understand the code.

        Ditto Python, Ruby, etc.

        If there wasn't a ready pool of talent, he'd go with Java in a second. Easier to find people, and you can handle a team mediocre programmers better. They will be less productive, but they can't do anywhere near as much damage.

        He's not alone in this viewpoint, nor is this a new perspective. It's the same kind of thinking that's kept Lisp in the gutter for 50 years.