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.
  • Very generally speaking, to me, a heavy mason user and a light TT user (but I do find them both useful), I see the difference as being TT encouraging your template/code abstraction to be more pure while Mason is more web geared and template directed. It's Mason's inheritence scheme that really makes me happy.

    Mason, I feel more like I'm writing web pages; TT I feel more like I'm writing logic. It's just how I feel about it =)
    --
      ---ict / Spoon
  • I've used both quite a bit for both pet- and Really Big projects.

    The elevator version:

    Mason is like PHP on steroids. And with perl syntax.
    In a web context TT is a balanced "MVC" toolkit for web applications.

    Mason is best as a "callback" system and TT is mostly used as a "pipeline" system. They can both be used as the other.

    In my experience "callback" is best for getting things done in a hurry. Mason is absolutely fantastic for this. I use Mason for quick web hacks all the time.

    6 months later I am
    --

    -- ask bjoern hansen [askbjoernhansen.com], !try; do();