4 ms·

"The Perl case, on the other side, is much worse. Migrating a relatively complex project from 5 to 6 is extraordinarily hard. It's probably the same as a whole

"The Perl case, on the other side, is much worse. Migrating a relatively complex project from 5 to 6 is extraordinarily hard. It's probably the same as a whole rewrite." One of the features of Perl 6 discussed in the article is "Fully backwards compatible with the use of Inline::Perl5". So why is it extraordinarily hard to migrate? I admit it is non-trivial, but the designers made it a key point to be backward compatible. No need to rewrite, Perl5 and Perl6 can co-exist in the same codebase. "There is no incentive for migration." Have you looked at the features Perl6 provides[1]? They may not seem valuable to you but it cannot be denied that the new features are plentiful and powerful from a programming language perspective. [1]http://www.perlfoundation.org/perl6/index.cgi?the_long_perl_6_super_feature_list http://www.perlfoundation.org/perl6/index.cgi?the_long_perl_...

ceronman 11y ago
Inline::Perl5 is just some glue to communicate to a Perl 5 interpreter from Perl 6. It's a simple form of inter-process communication between Perl 5 and 6. It's not that you can continue writing your Perl 5 program/library in Perl 6. This approach is not only really bad for performance, it's also very limited. For example, you can't just share data between both interpreters, however you can send some basic datatypes from one to the other. This has been done for other languages as well, for example, check Inline::Python [1]. It's an interesting thing, but not very useful for production. [1] http://search.cpan.org/~nine/Inline-Python-0.49/Python.pod http://search.cpan.org/~nine/Inline-Python-0.49/Python.pod
- cygx 11y ago
  You do have a point, but your description sells Inline::Perl5 short: For example, it is possible for Perl6 classes to inherit from Perl5 ones.
  - raiph 11y ago
    Note that Inline::Python for Perl 6 allows one to do likewise with Python. [1] "even PyQt's low level mingling finds all the information it needs and we can write programs using PyQt in Perl 6 :)" [1] https://github.com/niner/Inline-Python/commit/82cab4181d98f046c4529335f2c1748f1e89593c https://github.com/niner/Inline-Python/commit/82cab4181d98f0...

ceronman 11y ago

Inline::Perl5 is just some glue to communicate to a Perl 5 interpreter from Perl 6. It's a simple form of inter-process communication between Perl 5 and 6. It's not that you can continue writing your Perl 5 program/library in Perl 6. This approach is not only really bad for performance, it's also very limited. For example, you can't just share data between both interpreters, however you can send some basic datatypes from one to the other. This has been done for other languages as well, for example, check Inline::Python [1]. It's an interesting thing, but not very useful for production. [1] http://search.cpan.org/~nine/Inline-Python-0.49/Python.pod http://search.cpan.org/~nine/Inline-Python-0.49/Python.pod

cygx 11y ago
You do have a point, but your description sells Inline::Perl5 short: For example, it is possible for Perl6 classes to inherit from Perl5 ones.
- raiph 11y ago
  Note that Inline::Python for Perl 6 allows one to do likewise with Python. [1] "even PyQt's low level mingling finds all the information it needs and we can write programs using PyQt in Perl 6 :)" [1] https://github.com/niner/Inline-Python/commit/82cab4181d98f046c4529335f2c1748f1e89593c https://github.com/niner/Inline-Python/commit/82cab4181d98f0...