NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
I pour myself a cup of strong coffee. :-)
-- Jarkko Hietaniemi
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Actually No (Score:1)
Actually, MooseX::Declare is just another way to use Moose, but very surely not the primary.
Many people are using MooseX::Declare, and find it very nice and elegant, but many others (myself included) are not willing to use MooseX::Declare or Devel::Declare in production because it is not yet mature enough. Personally, my reasoning is that I feel it still exposes too much internals when it errors and makes for some difficult d
Re:Actually No (Score:1)
I agree, but that's not my main point here.
It is a mistake to canonize features before they're ready, unless you have some mechanism of indicating that they may change in subsequent releases. No one wants the chaos of frequent churn.
It's also a mistake, possibly more severe, to refuse to add features widely-requested and often reimplemented in subtly incompatible ways.
Having D::D available with core support is a good thing for experimentation. Yet it's also risky if that reduces the possibility of adding necessary, missing features. Part of that is, as Adam suggests, the fact of incompatibility across an ecosystem less tightly bound than the core. Part of that is the lack of good defaults for everyone but language adepts who know the proper incantations du jour. Part of that is that D::D can easily become a short-term safety valve to work around systemic process problems that may harm Perl 5 in the long term.
Reply to This
Parent