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.
  • Have a look at Mojo. I recently read somewhere that the author (sri) had written it with a Perl6 (port) in mind.
    • Thats correct, we have a full featured HTTP 1.1 stack ready to be ported to Perl6. (also including a Rack layer on the server side)
  • Don't forget the simple but effective 'Rack'. I find Rails and Merb etc to be too complex. If you need mod_perl like raw power, Rack is the way to go. I wrote about it at http://blogs.yellowfish.biz/2009/our-application-development-setup-and-why-json- rocks/ [yellowfish.biz]
    • I don't think you can compare mod_perl and Rack (both Rails and Merb are based on Rack these days btw.). Rack is all about running your code on different HTTP servers using a unified api, while mod_perl gives you the power to hook into the guts of Apache and change low level logic.
    • Well if you like Rack then you should be looking at HTTP::Engine or Mojo for Perl equivalents.
    • It might please you to learn that Web.pm aims to have a full port of Rack at its core. The idea is that people should be able to choose the level of abstraction they want to build their web app on. The levels are something along the lines of:

      • A minimal setup. (Rack.)
      • Templating.
      • MVC.

      That last level is the reason I'm investigating MVC frameworks at present.

      • If your aim is to have a full Rack port maybe you should call it Rack or Web::Rack? Web.pm seems a bit too generic, after all there will be alternatives and they'll need a namespace too.
        • Noted.

          For various reasons I'm not inclined to discuss the naming of Web.pm via a blog commenting system. I'll happily move the discussion to IRC or email, though.

      • That, my dear friend, will be awesome. Mod_perl is great but a web server agonstic and low level web framework like Rack or Servlets will make Perl shine again (and a bit of slick marketing!).
  • Scaffolding sure looks amazing in Screencasts, but what you shouldn't forget is that the ORM agnostic Merb was pretty much about to beat Rails when they decided to merge both projects.
    • I know nothing about Merb, except that it was merged with Rails. In particular, from your comment I still am no wiser as to why scaffolding is bad, or why Merb was successful due to its lack of scaffolding.

      Guess I'll have to read up a bit on Merb. Or what's left of it. :)