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.
  • 1st let me say I DO have a right to spout because I, for one, actually did write a large portion of Parrot from 01 to 04.

    >There aren't enough people to do the work.

    Chromatic, you are only half right, or maybe you are right now, but retroactively wrong. There WERE enough people to do the work. Dan left after I left for the same reason that I left. People issues. Leo is very likely a great guy, in person, but he was hard to work with, and he was just plain rude over email. So now he is the patch monster with full reign.

    When you come along and join an open source project, and stand on other folk's shoulders, there is an important thing to bring with you, respect and courtesy, especially to those who wrote the "poor mess" that you are trying to improve upon. There was a distinct lack of this going on, and I'm not the only one that dealt with it.

    That is the real elephant in the room, IMO, but only the original coders knew about it because it was kept off list.

    Parrot, grandiose? I don't think so. A huge mess, yes. If you want specifics, I can go into them, but what everyone touts as grandiose design is simply not so. Continuations are not so big a deal, as I initially implemented them in a matter of hours. People tout this as one of Parrot's grand design decisions, but I don't agree. That is a point of view from the outside looking in. The real problem was lack of comradery, teamwork, communication and respect. None of that is technical, but the effect it had was to reduce the number of technically capable people who care to help.

    Thanks for bringing up the subject, though. :)