in reply to Re^5: Perl 6 and performance
in thread Perl 6 and performance

What exactly has the state of the Parrot VM to do with Perl 6, which is a language specification?

Replies are listed 'Best First'.
Re^7: Perl 6 and performance
by educated_foo (Vicar) on Feb 09, 2012 at 19:54 UTC
    Which implementation of said specification is least buggy and incomplete now?

      Depends on the area you look at. But what does that have to do with Perl 6 (which, again, is a language, and not a compiler) being ignorant of prior art?

      Your criticism comes out like saying "C is not <adjective>" because a C compiler you happen to have worked with isn't <adjective>. Which isn't very educated at all.

      I'm happy to revise my decision if you can come up with several examples that illustrates where the Perl 6 designers are ignorant of prior art.

        I'm happy to revise my decision if you can come up with several examples that illustrates where the Perl 6 designers are ignorant of prior art.

        You're drawing a very fine distinction between somewhat disjoint groups: Perl 6 designers, Perl 6 implementors, and Parrot implementors. Outside of #perl6 and perhaps #parrot, no one cares about this distinction. In truth, that finger pointing is one big reason for my disillusion with the whole thing.

        For a common programmer. Perl 6 means a program that runs everything as defined in the Perl 6 manual. Very few people would bother to know the difference between a specification and implementation.
        Okay, let's try to be "technically correct" (the best kind!).

        I'll choose my favorite C or Java compiler -- you choose your favorite Perl 6 compiler. Does it do profile-guided optimization? Polymorphic inline caches? Real-time garbage collection? Can you even explain these things? Yeah, I didn't think so. Please see GCC and Sun's Java for prior art.