So, I finally got around to reading the introduction that dams put together for p5-mop.  (If you don’t know what that is, it’s the effort to get a MOP, or “Meta-Object Protocol,” into the Perl 5 core.  This would not be adding Moose to Perl 5, but it would be adding something that would make Moose—or any competitors—a lot more feasible, efficient, and user-friendly.) I’ve been following Stevan’s blog posts about the ongoing work, but a lot of times those are more about certain implementation details.  They’re very useful, and very interesting, and I hope he continues to do them, but sometimes they can be a bit forest-for-the-trees, if you see what I mean.  I think it was great of dams to give us a 6,000 foot view, as it were.

Now, I haven’t had the opportunity to try out p5-mop myself yet, although I certainly hope to sometime soon.  So, as you read my thoughts about the MOP features that dams describes for us, remember that this is a more of a first-impression reaction and less of a practical response after use.  Still, I’ve been thinking about these sorts of things for many years now, so these are not off-the-cuff comments either.  It’s definitely a section-by-section reply to dams’ post, though, so make sure you’ve read that first.

Ready?  Excellent.  Here’s my impressions of the P5 MOP so far.