use Perl

• Go Enterprise (Score:1)

  by jplindstrom (594)

  I'd like to see "Perl Enterprise Patterns" or something equally buzzword compliant lying on my desk.
  
  It would probably be an interesting read, but mostly I would just use it to subliminally fade the script/unreadable/toy/fringe aura Perl has in too many people's minds.
  • Re:Go Enterprise (Score:1)

    by wnodom (2030) on 2004.07.13 10:52 (#32468) Homepage Journal

    Funny you should mention this; Andy Lester and I were talking about it just a couple of days ago.

    We both want this book, for two main reasons:

    • We want a quality guide we can hand our developers and say "Build Perl applications this way."
    • We want to establish greater credibility for Perl with management, to show that "enterprise applications" can and should be built with Perl.

    In case anyone's interested, here are some notes [tmtowtdi.com] that I wrote along these lines quite a while back.

    --Bill

    Reply to This

    Parent

    • Re:Go Enterprise (Score:2)

      by Ovid (2709)

      Possibly one of the biggest problems I can see with a book like that is the average Perl developer. For Java, I think you can really get away with having developers less skilled than many and still have a bit of safety. Encapsulation, type-safety and checked exceptions are examples of constraints that simply don't exist naturally in Perl, but are the safety net for the Java programmer. This also means that the Java programmer must weave that safety net rope-by-rope or he's not allowed to do his acrobatic
      • Re:Go Enterprise (Score:1)

        by chromatic (983)

        Having actually seen "enterprise-class" Java, I label the parent post "-1, Unnecessary Community Self-Loathing".

        Trust me, there are enough terrible and dedicated programmers in the world to jump through Java's hoops to produce absolutely hideous code.