Well, although I do not find Jade’s syntax any better than TT’s ... in many ways it is notably worse ... there’s always gonna be room for one more tool that does the same thing, and I guess that Perl had better support it also.   Proceed apace, then, to finish the entire implementation of every feature.   (I worked with an extremely well-known company that ran headlong into todo’s in the released Ruby “gems” that it was trying to use to supersede a Perl program that worked perfectly well.   Let’s just be sure Perl doesn’t commit that same sin.)

Aside:   One thing about this biz that has always amused me is that there never is one standard way to do anything.   Lately, PHP is “outy” and Ruby on Rails seems to be “inny,” which only means that, in another year or so, Haskell will be next.   Or something.   I’ve totally lost count of the number of website-framework systems that are out there, all doing more or less exactly the same thing in exactly the same way, all claiming to be the best.   And, gosh whodathunkit, we can use macro substitution(!!) to build CSS without repeating ourselves.   Sounds like a good place for a <<<HEREDOC in just about any existing language that you please, does it not?   Uh uh.   We must have a special language – no less than three syntactically-incompatible ones and stay-tuned for more – just to do that trivial chore, and the creators title each to more or less reflect their (or, their ...) “awesomeness.”   You have to go with the flow, but there’s still a lot of absurdity in it all.   :-D