use Perl

• One idea (Score:2)

  by djberg96 (2603)

  What is interesting now?

  Parallel processing.
• Mostly client-side (Score:1)

  by perrin (4270)

  The server-side of web development hasn't changed significantly in years. What has changed is the client-side. The complexities of CSS and the desire to actually use JavaScript are the main new developments in the web game. They also tend to be a real time-sink, but there's no putting Google Maps back in the box now.
  • Re: (Score:2)

    by ask (83)

    Yeah, client-side stuff. On the server side a lot of the talk is about frameworks and tools that, IMO, have way too much magic. I don't think they help all that much getting your work done - as you said, the basic paradigm is still the same. I haven't tried it, but with Jifty they are trying to change that a little, but I'm not sure it's sane to try hiding or abstracting the reality of how HTTP works that much...
    
    Anyway,
    
    You used XML to push data around in your back-end with AxKit -- now you use JSON to

    --
    

    -- ask bjoern hansen [askbjoernhansen.com], !try; do();
    • Re: (Score:1)

      by Aristotle (5147)

      Personally I like Catalyst better, and like Catalyst, because it gets away with quite little magic (unlike Jifty), but it has neat provisions to make your code very, very non-repetitive. Dispatch-type Chained is the bomb; it has helped clean up my code (that was already reasonably well-structured) to a similar extent as going from procedural to object-oriented in a GUI app (and I don’t mean messy procedural code).
• Non blocking event based servers (Score:1)

  by Phred (5358)

  Oh wait, you already wrote one (or two) of those IIRC :) Still seems like pretty cool stuff. I've been watching libev recently and have been tasking myself to try it out.