Acme-oop-ism Part Two: Type::Tiny

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…

Acme-oop-ism Part One

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…

Introducing Moops

Moops is sugar for writing object-oriented Perl. It provides similar syntax to MooseX::Declare and Stevan Little's p5-mop-redux. It's some glue between Moo, Type::Tiny, Function::Parameters and Try::Tiny, but for those occasions when you want the backing of a meta object…

Data::Dumper::GUI

Everyone knows all that command-line stuff is for weirdo geeks, right? 😉 So let’s bring Data::Dumper kicking and screaming into the 21st century and give it a pretty GUI! Introducing Data::Dumper::GUI; a GUI for Data::Dumper. It allows you to view…

Introducing Type::Tiny

Type::Tiny is a tiny (no non-core dependencies) framework for building type constraints. OK, probably not that exciting. How can I grab your attention? Rate WithMoose WithMooseAndTypeTiny WithMoose 8071/s — -25% WithMooseAndTypeTiny 10778/s 34% — The benchmark script is shown…

Sugar for MooseX::Traits

Tomorrow morning I'll be needing to get up in the wee small hours of the morning to travel to the Moving to Moose Hackathon 2012. In the mean time, here's some sugar for the awesome MooseX::Traits… package traits; use MooseX::Role::Parameterized;…

Perils of Plugins

Plugin-based architectures can be a bad idea. Not always. In user-facing applications, where the list of installed and enabled plugins is clear, then plugins are often a good thing. This article is concerned not with end-user facing applications, but with…