Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Okay, here are more Model Users: =head2 "Sam": Python implementor Sam has a favorite language, Python, and he wants to target it to Parrot. Sam: * is only interested in Parrot if it's faster than CPython =head2 "Rasmus": PHP implementor Rasmus has a favorite language, PHP, and he wants to target it to Parrot. Rasmus: * wants to replace Zend with Parrot for PHP 6
    • by milardj (4452) on 2005.06.14 9:07 (#41129) Journal
      I think you raise a great point for reminding people that Parrot is not just a Perl VM.

      I'm not sure you have "Sam's" (and lets add "Matz") motivation correctly. Speed is obviously a factor but the biggest thing I keep hearing (especially from the Ruby crowd) is access to CPAN. So speed *and* transperant language interoperability where by the latter I mean if you provided stubs for the external code then your script would run as is with CPython or the Ruby interpreter.

      To me language interoperability is still the great unknown in terms of mechanics and in terms of how tightly|loosely contstrained it will be.

      I remember that one of Sam's constant complaints was that Perl6-centric decisions were being made that made it more onerous to accomodate Python. I have no details just dimly remembered (!sharp!) e-mail exchanges between Sam and Leo.

      • Well, Parrot will never be Perl6-specific, but without the Perl installed base, Parrot won't ever reach its potential.

        "Too many priorities is no priorities."