Re: Anachronistic Acronyms in Parrot?

[Guido van Rossum]

> The cultural differences are completely irrelevant. If we produce a
> tool that's fast and efficient, and you can and want to use it, go
> ahead and use it. Nobody's going to stop you. And if you can't or
> don't want to use it, hey, not a problem, we've still got an
> interpreter *we* can use and nobody's lost anything. 'course,
> someone else might end up writing a Python compiler to it anyway. :)
> 
> Of course, if you want to help out, that would be very cool; but if
> not, and the development's mainly fueled by Perl people, you only
> have yourselves to blame if it ends up being too
> Perl-centric. (Well, you can also legitimately blame me, because I'm
> trying my damnedest to stop that from happening, but it's impossible
> for me to see the intricate details of every dynamic language out
> there.)

If your view on coding style makes the code impenetrable for me, I
blame you, not myself. :-)

--Guido van Rossum (home page: http://www.python.org/~guido/)