If you’re not in the Perl community it’s a running joke that every programmer has to implement either a templating module or a wrapper around DBI. While one of the Perl mottos is “There’s More than One Way to Do It” the sheer number of templating modules on CPAN is staggering, particularly considering the utility and maturity of the kick-ass Template Toolkit.
So imagine my surprise when hitting the recent modules page to find Class::Skin. This author not only breaks the unwritten rule about templating modules but he's somehow convinced himself that a templating module belongs under the Class:: hierarchy, normally reserved for OO framework and similar modules. Stop the insanity!