Re: Re: Re: message from Parrot PieThon developer

Lenard Lindstrom wrote:

> The current build process requires Perl5. I have cygwin and find its
> Perl
> causes page faults on my system. So I have not successfully built
> Parrot. Even before the page faults it was trying for a cygwin build
> with gcc. This can
> be overridden, but there are not explicit instructions for doing a
> mingw build
> like I wanted, let alone a VC build. But I am sure a win32 build will
> become a priority if you are interested in using Parrot. Parrot is
> certainly worth looking at.

You really make it sound inviting (not).  They have a real-time automated
system that checks out from cvs and does builds every 15 minutes on 6
different OS's and reports the results on a timeline on the web, called
tinderbox.  It's a really exciting graphic tool that shows every fifteen
minutes that Parrot doesn't build on 5 of the 6 OS's. :-)

I read the Parrot talks to learn more about it.  The papers make Parrot
sound like the answer to world peace and anti-gravity until you look at the
dates.  The papers were all given two years ago and there has been no
progress since then.  Prothon has gone from a stupid idea to where it is (a
stupid interpreter?) in 8 months.  Should I hitch my wagon to something so
risky?

The big problem is that switching to Parrot is a one-way decision for me.  I
don't have the luxury of doing it as a research project on the side.  I
either stick with APR or jump to Parrot and live or die with Parrot.  If I
jump to Parrot and it takes years to finish or never finishes, then Prothon
is doomed.  I can't take that chance.