comment on

Aren't you in danger of just further dilluting the gene pool?

Certainly... but I really don't see it as a bad thing. Each one of the efforts that tries to bring Perl 6 to life gets it from a different perspective, and the experiences from each of this projects are creating a more powerfull knowledge of the Language and the runtime requirements for it.

Eventually all this projects will implement the full Perl 6 at the same time, even because most of the people working in this projects knows each other and do share experiences.

And finally, the idea of having alternative runtimes is interesting. Let me bring one considerable difference from Parrot to YAP6. Parrot implements trace gc and YAP6 implements refcount gc. Trace gc may be more efficient and more safe, but is not deterministic. Some applications may need a more deterministic approach to memory use versus processing time.

daniel

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

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Don't ask to ask, just ask
	PerlMonks