Permalink
Browse files

try to fix page generation

  • Loading branch information...
1 parent 9bbf6e9 commit 7b40654e9cee001c12a6236b1ad36860ffb1abd6 @dams committed Sep 16, 2013
Showing with 0 additions and 24 deletions.
  1. +0 −24 _posts/2013-09-16-p5-mop-a-gentle-introduction.markdown
@@ -21,27 +21,3 @@ Stevan Little says:
> instead we want to put a minimal and less opinionated MOP in the core that is
> capable of hosting something like Moose
-As far as I understood, after a first attempt that failed, Stevan Little
-restarted the p5-mop implementation: the so-called p5-mop-redux
-[github project](https://github.com/stevan/p5-mop-redux), using
-[Devel::Declare](https://metacpan.org/module/Devel::Declare), ( then
-[Parse::Keyword](https://metacpan.org/module/Parse::Keyword) ), so that he can
-experiment and release often, while keeping the implementation core-friendly.
-Once he's happy with the features and all, he'll make sure it finds its way to
-the core. A small team (Stevan Little, [Jesse Luehrs](http://tozt.net/), and
-other contributors) is actively developping p5-mop, and Stevan is regularly
-[blogging about it](http://blogs.perl.org/users/stevan_little/).
-
-If you want more details about the failing first attempt, there is a bunch of
-backlog and mailing lists archive to read. However, here is how Stevan would
-summarize it:
-
-> We started the first prototype, not remembering the old adage of "write the
-> first one to throw away" and I got sentimentally attached to my choice of
-> design approach. This new approach [p5-moop-redux] was purposfully built with
-> a firm commitment to keeping it as simple as possible, therefore making it
-> simpler to hack on.
-> Also, instead of making the MOP I always wanted, I approached as building the
-> mop people actually needed (one that worked well with existing perl classes,
-> etc)
-

0 comments on commit 7b40654

Please sign in to comment.