Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • You are certainly entitled to your opinion and I wont try to convince you to use Moose as I am sure your opinion is not knee-jerk, however I would like to just address a few points.

    To start with, Moose is still a work in progress and is in no way up to the level of sophistication as say a full blown language, so there will be some dark and ugly corners sometimes. Some of the things we are currently working on are both startup speed (we can't reduce the "bloat", but we can at least make it less noticable)

    • Hi Steven,

      Thanks for taking time to read and comment on this. I'm often the voice of dissent (I hate POE, the various ORMs, Parrot, and lots of other stuff, too). So I'm always a bit surprised when I'm not dismissed as a crank =)

      Switch might be a source filter, but it's small and has no deps. As to whether Moose is as fragile as it, I can't honestly say. That was a bit knee jerk of me to say that. But to the extent that the analogy does hold (which might not be far), I'd like people to consider not releasing modules that depend on Moose without a good reason. Using Inline::C vs XS probably would have been a better example. Even though Inline::C works pretty well, just out of respect for the time and energy of people using modules, it's better to use XS than Inline::C in CPAN modules. Again, most modules aren't used because they're the coolest thing ever, but instead because they're a dep of something else.

      Anyway, I did write that Moose is good for prototyping these ideas, mechanism, and the syntax. I didn't mean to suggest that Moose shouldn't exist or is inherently bad. I'd just like to see people being realistic about it's cost -- like the old saying goes, Lisp programmers know the value of everything but the cost of nothing. Part of the cost is the little leaks that the abstraction does inevitably spring.

      I am glad to see interest in fixing up OO in Perl -- capabilities, sugar, and everything.

      Cheers,
      -scott

      • Again, most modules aren't used because they're the coolest thing ever, but instead because they're a dep of something else.

        When you write insightful things like this, I can never take you as a crank. Like you say, only when abstractions leak is this a problem.