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.
  • I think even someone not into computing, perhaps especially so, would be able to pick up on the conflicting messages being emitted about P6. Much of the problem is due to the 'if we ignore it it'll go away' philosophy coupled with those deeply involved with certain integral parts of the project speaking much more openly and candidly in dark corners with trusted listeners. Parrot is the poster child of this problem and it, indeed, raises significant doubts about the p6 project as a whole. Problems that everyone involved knows about but won't discuss publicly lead it nowhere good. Those without near-religious dedication to Perl likely sense this with even the most cursory observations and will probably move on without a compelling reason to stay.

    Because P6 has taken the tack of forgetting its original impetus and refusing to acknowledge publicly the problems and rumours that plague it much in the same way as the current US administration, it has become something of a quixotic exercise in academic wankitude. Whether or not it will be the Snobol of the 2000s or 2010s remains to be seen.

    • speaking much more openly and candidly in dark corners with trusted listeners

      People do that about employers too, so I'm not sure if this activity in itself is really saying anything about the project.

    • I agree, and my entire effort in Perl6/Pugs/Parrot development has been refusing to participate in closed lists, communicate solely in public channels, and strive to bring everyone involved into those public channels (e.g. getting leo and TimToady on IRC).

      I'd say by working with p5p, we are getting back to the route of expressing the parts of Perl6 that actually solves real-world problems (class introspection, fast method calls, named params, constraints, macros) into Perl5 land, and the surface syntax --

      • You are but one. This is me being optimistic. :) Still, the original complaint that there are loud and conflicting messages throughout the project as a whole is real and valid. People talk and especially when those people have a bit of credibility one must consider that perception is reality.
        • I wouldn't characterize my posting as a "complaint" per se, merely an observation. I recognize that a great deal of chaos is needed in order for our community process to work – in the end it usually works itself out to a better-than-favorable solution. Regardless, my whole point in posting this is to say:
          1. yes, the community is divided on the future of perl 6 and parrot, though I'm not making any value judgement on that;
          2. here is a sampling of the matrix of opinions I have encountered (mostly tal