in reply to Questions On the Perl VM, Parrot, .Net, and the JVM...
The problem is that the Java VM (and the .NET CLR) is very much tied to static typing. If you take a look at Perl.NET, it has to extend the language (via POD markup) to indicate the signature of methods so that the compiler can know how to type methods. This is a really hard problem - do you use something like that and downgrade everything to "Object" (to use Java terminology) methods and fudge a slow layer on top of that, or create our own VM, with its performance focussed on dynamically typed languages. I'd go with Parrot. Not only that, but Parrot is free, in every sense of the word.
|