Sam's Blog > Template-sandbox

October 2010 Perl Template Roundup Released

Sam Graham — Sun, 07 Nov 2010 16:10:00 GMT

Having been a little busy for the past month and a half, my attempts to do the next Perl Template Roundup got delayed from September into October, partly by adding a number of new engine plugins to Template::Benchmark:

Support for pure-perl mode Text::Xslate was also added and two new cache-types for Template::Sandbox (Cache::FastMemoryCache and Cache::Ref::FIFO).

Then I had to sit around and wait for spare CPU time to actually run the multiple-days of benchmarks, unfortunately this clashed with me using that computer as I rushed to release stable versions of my other projects in anticipation of being too busy starting my new job.

Once the projects were out the door I could run the benchmarks, which completed mid-October, just in time for that whole "too busy" thing to kick in as I tied up loose ends before my start date.

Anyway, it's now November, and I figured I ought to do something about these reports... so here you go: the October 2010 Perl Template Roundup (belatedly).

Perl Template Roundup Announced

Sam Graham — Thu, 01 Jul 2010 07:28:00 GMT

Having gone quiet for a month, I've managed to avoid distraction enough to release a project which had been stubbornly stalled for the past couple of months: a Perl Template Roundup.

Based on Template::Benchmark it's an exhaustive (and exhausting) bunch of benchmarks for a collection of Perl template engines, sliced this way and that way by feature, caching, phase of the moon, and anything else I could measure.

Template::Benchmark.pm v1.00 Released

Sam Graham — Mon, 10 May 2010 16:22:00 GMT

Well, after 13(!) point releases, I'm happy enough with Template::Benchmark to make the first stable release.

v1.00 should be hitting a CPAN mirror near you sometime soon.

Now that it's officially released, I thought I'd go into a little more detail about what Template::Benchmark does, how it can be useful to you, what motivated me to write it in the first place, and some thoughts on where to take the project next.