3 ms·
> It's a great tool if you work in the JVM ecosystem and want to play around as a language designer. Except that it's not really exposing much of the JVM from
by kbenson 10y ago
> It's a great tool if you work in the JVM ecosystem and want to play around as a language designer.
Except that it's not really exposing much of the JVM from what the article mentions, it just uses the JVM as a base. That is, Truffle languages can talk to other truffle languages, but I'm not sure how easy it is for a truffle language to talk to a JVM language.
From everything I read, it seems like people thought Parrot was a good idea so decided to rewrite/reimagine it using the JVM instead of C as a base.
- zzzcpan 10y agoI liked Parrot, but it didn't move in the right direction. No useful AOT and JIT from the start kind of turned me down.
- kbenson 10y agoWell, those were always planned features, they just never got around to them, or they never got enough attention before the project basically died out. As for not moving in the right direction, it was probably far too ambitious to try to develop something like Parrot and something like Perl 6 at the same time, with dependencies on each other. Both projects would have been better served if they did their own things, and Parrot was just seen as "a good candidate for a second implementation" from the Perl 6 perspective, rather than the primary target. It's hard to target a VM that's not done, and it's hard as a VM to support a language that isn't finalized (and has crazy requirements).