This is an automated email from the git hooks/post-receive script. gregoa pushed a commit to annotated tag release-0.006 in repository libclass-tiny-perl.
commit 12e5ff586dc231bc1928b8e74451a245b7a0def9 Author: David Golden <dagol...@cpan.org> Date: Thu Sep 5 11:56:43 2013 -0400 more rationale revisions --- README.pod | 22 +++++++++++----------- lib/Class/Tiny.pm | 22 +++++++++++----------- 2 files changed, 22 insertions(+), 22 deletions(-) diff --git a/README.pod b/README.pod index 12982e7..ef7ec6a 100644 --- a/README.pod +++ b/README.pod @@ -287,17 +287,17 @@ else, this is smaller in implementation and simpler in API. =head2 Why this instead of Moose or Moo? -L<Moose> and L<Moo> are both excellent OO frameworks. L<Moose> offers a -powerful meta-object protocol, but is slow to start up and has about 30 -non-core dependencies including XS modules. L<Moo> has a simpler meta-object -protocol and is faster and lighter at about 10 non-core (but pure Perl) -dependencies. - -By contrast, Class::Tiny has no meta-object protocol, minimal class -introspection, and has B<zero> non-core dependencies for Perls in the L<support -window|perlpolicy>. It has far less code, less complexity and no learning -curve. If you don't need or can't afford what Moo or Moose offer, this is a -intended to be a reasonable fallback. +L<Moose> and L<Moo> are both excellent OO frameworks. Moose offers a powerful +meta-object protocol (MOP), but is slow to start up and has about 30 non-core +dependencies including XS modules. Moo is faster to start up and has about 10 +pure Perl dependencies but provides no true MOP, relying instead on its ability +to transparently upgrade Moo to Moose when Moose's full feature set is +required. + +By contrast, Class::Tiny has no MOP and has B<zero> non-core dependencies for +Perls in the L<support window|perlpolicy>. It has far less code, less +complexity and no learning curve. If you don't need or can't afford what Moo or +Moose offer, this is a intended to be a reasonable fallback. That said, Class::Tiny offers Moose-like conventions for things like C<BUILD> and C<DEMOLISH> for some minimal interoperability and an easier upgrade path. diff --git a/lib/Class/Tiny.pm b/lib/Class/Tiny.pm index 0d2bb80..5f5e5e5 100644 --- a/lib/Class/Tiny.pm +++ b/lib/Class/Tiny.pm @@ -387,17 +387,17 @@ else, this is smaller in implementation and simpler in API. =head2 Why this instead of Moose or Moo? -L<Moose> and L<Moo> are both excellent OO frameworks. L<Moose> offers a -powerful meta-object protocol, but is slow to start up and has about 30 -non-core dependencies including XS modules. L<Moo> has a simpler meta-object -protocol and is faster and lighter at about 10 non-core (but pure Perl) -dependencies. - -By contrast, Class::Tiny has no meta-object protocol, minimal class -introspection, and has B<zero> non-core dependencies for Perls in the L<support -window|perlpolicy>. It has far less code, less complexity and no learning -curve. If you don't need or can't afford what Moo or Moose offer, this is a -intended to be a reasonable fallback. +L<Moose> and L<Moo> are both excellent OO frameworks. Moose offers a powerful +meta-object protocol (MOP), but is slow to start up and has about 30 non-core +dependencies including XS modules. Moo is faster to start up and has about 10 +pure Perl dependencies but provides no true MOP, relying instead on its ability +to transparently upgrade Moo to Moose when Moose's full feature set is +required. + +By contrast, Class::Tiny has no MOP and has B<zero> non-core dependencies for +Perls in the L<support window|perlpolicy>. It has far less code, less +complexity and no learning curve. If you don't need or can't afford what Moo or +Moose offer, this is a intended to be a reasonable fallback. That said, Class::Tiny offers Moose-like conventions for things like C<BUILD> and C<DEMOLISH> for some minimal interoperability and an easier upgrade path. -- Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-perl/packages/libclass-tiny-perl.git _______________________________________________ Pkg-perl-cvs-commits mailing list Pkg-perl-cvs-commits@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-perl-cvs-commits