note broquaint <blockquote> 1. CPAN modules that will not work with Perl 6/Parrot. </blockquote> While this is not likely to be true at launch, within a year or so Parrot should be happy to load Perl5 code therefore making the majority (if not the entirety, depending on how XS dependant modules are handled) of CPAN available to Perl6. <blockquote> 2. It seems that everyone is writing their very own VM these days (ex: java, .net, mono, parrot), which will (of course) run faster, better, etc than everyone elses. There is hardly a practical technical incentive (platform dependency excluded) to choose one VM over the other. Parrot will be just one in the crowd. </blockquote> For the reasoning behind Parrot as YAVMI1 see [Elian]'s [http://www.sidhe.org/~dan/blog/archives/000151.html|(Perl|python|Ruby) on (.NET|JVM)], [http://www.sidhe.org/~dan/blog/archives/000152.html|(closures) The reason for Parrot, part 2] and [http://www.sidhe.org/~dan/blog/archives/000158.html|Why not a Lisp (or Scheme) VM for Parrot?]. <blockquote> 4. Will not appeal to perl programmers because it will probably be bigger, require more typing, run slower than perl 5. </blockquote> Slower than perl5? To quote [Elian|the man himself] - Parrot is an order of magnitude faster than perl 5 doing equivalent things. Without enabling any extraordinary measures. (see. [http://www.sidhe.org/~dan/blog/archives/000139.html|Now I know how the Lisp folks feel]). <blockquote> 5. They are not really thinking about making extending/embedding easier than XS. </blockquote> Parrot won't use <tt>XS</tt>, so this is a non-issue. HTH <tt>_________ broquaint</tt> 1 Yet Another Virtual Machine Implementation 261631 261798