use Perl

• My guesses ... (Score:2)

  by autarch (914)

  I've found the whole Rails thing pretty silly myself. It looks like a very nice tool for certain apps, but I really don't think it'd help much at all for apps with complex, large databases, for the same reason I don't think Class::DBI works well for in those cases.
  
  My guess as to why Rails is so hot is several-fold:
  
  - The folks using it make very pretty products. Basecamp looks great, as does the Ruby on Rails site. I wish Perl sites and apps looked that good, and I really wish mine did!
  
  - If you've been us
  • Re:My guesses ... (Score:1)

    by perrin (4270)

    I think Maypole actually came well before Rails. Before Maypole, there was OpenInteract and Apache::PageKit, and of course all the others (like Mason) that aren't quite so squarely aimed at MVC apps.

    It doesn't bother me that Rails is doing well. What does bother me is when these guys make it sound like they invented this stuff, and no one else has it. And, as you say, people who have never worked on large web apps seem totally willing to believe that Rails is the only thing that ever had had this stuff.
    • Re:My guesses ... (Score:2)

      by TeeJay (2309)

      Before I start I should declare my vested interests - I use and maintain Maypole :)
      
      Looking at the actual releases - Maypole 1.0 was released in Febuary 2004 and Rails wasn't released until April 2004, although development on what would become Rails was probably started 3 to 6 months before Maypole development was started.
      
      I think Maypole is already more flexible in it's vanilla setup than Rails in it's vanilla setup.
      
      The maypole developers need to keep an eye on Hibernate and Catalyst, as they are breaking ne

      --
      
      @JAPH = qw(Hacker Perl Another Just);
      print reverse @JAPH;