Acme-oop-ism is about writing code that works in Moose, Mouse and Moo. We've already looked at how Type::Tiny has achieved this. Now I'm going to introduce you to some Acme-oop-ist techniques.

Acme-oop-ism is about writing code that works in Moose, Mouse and Moo.

Type::Tiny was born of frustration with how MooX::Types::MooseLike handles "inflation". Inflation is how Moo handles interacting with Moose. I'm simplifying here, but when Moo detects that Moose is being used, it builds a Moose::Meta::Class for each Moo class you've defined, and a Moose::Meta::Role for each role.

Ingy gave a talk on Acmeism at YAPC::NA. Acmeism is a simple, yet ambitious idea. Break down the barriers that exist in programming by publishing software modules that work in multiple different languages. (And use smarter tools so that that doesn't have to be so burdensome.)

I'm writing to tell you about Acme-oop-ism. A somewhat less ambitious idea, but perhaps one that you'll like anyway.

Welcome to the second edition of Planet Moose, a brief write up on what's been happening in the world of Moose this month, for the benefit of those of you who don't have their eyes permanently glued to the #moose IRC channel, or the MetaCPAN recent uploads page.

Thanks for contributions from Damien Krotkine and Stevan Little. If you'd like to contribute some news for next month's issue, you can do so on the wiki.