I lurk on the perl6 internals list, and I must say that I have to clear that folder *often* because of its activity. So what if it takes 1, 2, or even 6 years to get a stable parrot platform. The benefits of such a platform are great enough to wait. Besides, what is the rush? The current Perl is great, and because of the Ponie project, you *should* not even have to rewrite your Perl 5 wizardry in Perl 6.

Parrot is going to be a long term project, and before Perl 6 comes out, Parrot has to be a stable *platform*. This could take years, and since there is no dire need for the next generation of Perl, I think that we can exercise some patients.

May I suggest lurking on the perl6 internals list?

With that being said, I am more excited about Parrot than Perl 6 because if it accomplishes its goal, it will usher a whole new era of "write once, run anywhere" like Java was *supposed* to do...

BTW, if anything is dying, it is *BSD ;) .. j/k

---

---

• 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.