http://www.perlmonks.org?node_id=658983


in reply to Re^2: YAP6: A p5 approach to p6
in thread YAP6: A p5 approach to p6

The thing in my lay, and completely unqualified, perspective that parrot should have done different is target a HLL from day 1.

I agree, but remember that most of the reason that we're making such progress on tangential projects right now is that we have the Parrot compiler tools featureful and stable enough to allow us to build or port languages quickly.

I failed to mention that I doubt YAP6 is necessary.

It may or may not succeed, but the people who are working on it might not work on Parrot or vice versa. Concurrent evolution and exploration might not be the most efficient use of global resources, but there's rarely a central planning agency that can convince everyone to go in the same direction.

Replies are listed 'Best First'.
Re^4: YAP6: A p5 approach to p6
by flexo (Sexton) on Dec 25, 2007 at 22:23 UTC
    but the people who are working on it might not work on Parrot or vice versa. Concurrent evolution and exploration might not be the most efficient use of global resources, but there's rarely a central planning agency that can convince everyone to go in the same direction.

    True. Opportunity cost. That said, a couple of emails from principal devs, along the lines of:

    "Is there currently anything keeping you from joining our project? Is there anything you see us doing incorrectly that you might be able to help fix?".
    might gain a contributor or two. Well, wouldn't do any harm, anyway.

    Heh. Reminds me of the old used-car salesman pitch (paraphrasing) : "What do we need to do to get you into this shiny new (still under-development) Parrot, today?". :)

        I was posing the question from the point of view of a Parrot developer asking a prospective contributor what it would take to get them to join the Parrot effort.

        What sort of discrete parcel of effort do you think a prospective contributor is looking for from the current Parrot team?