Re:Perl 11
by rurban on Wednesday October 24, 2018 @04:25AM
(#18290586)
perl 11 came from 5+6=11, which was Ingy's idea. Will (rperl) and I (cperl, parrot) liked it, so we sticked to it. We are three.
The idea was to come up with something like pypy performance-wise (i.e. parrot done right without all the destruction done later) and perl6 feature-wise.
perl6 is THE picture for cperl, because it has a proper spec for the useful features, to void the usual bike shedding, plaguing p5p since day 10.
The picture for RPerl is not perl6 but performance, proper mapping of perl5 code to C++ data and algos, eliminating run-time magic.
The other projects are doing their thing also, which is fine and encouraging.
Re:Perl 11
by SwellJoe on Wednesday October 24, 2018 @03:51PM
(#18295771)
Thanks for the clarification. I know Will, as we currently live in the same city, but I haven't followed development of any of the projects mentioned very closely.
The idea was to come up with something like pypy performance-wise (i.e. parrot done right without all the destruction done later) and perl6 feature-wise.
perl6 is THE picture for cperl, because it has a proper spec for the useful features, to void the usual bike shedding, plaguing p5p since day 10.
The picture for RPerl is not perl6 but performance, proper mapping of perl5 code to C++ data and algos, eliminating run-time magic.
The other projects are doing their thing also, which is fine and encouraging.