logoalt Hacker News

stakhanov • today at 2:39 PM • 1 reply • view on HN

I think it's all about corpus weight.

When Python did the migration, it had a good flow of new investments coming into it and delivered good reasons for why those should go to Python 3 rather than 2. At the same time, it also already had a base of existing investments in Python 2 delivering better ROI without the added cost of a migration, and the sum of that exceeded the critical mass it took to make it economical to keep both versions of the ecosystem around.

With Perl you are seeing what it looks like when you have zero new investments coming in and no good reasons for why new investments should go to Raku. (Because: Just use Python). You do still have a non-negligible base of existing investments in Perl 5 and those deliver better ROI without the added cost of a migration. So my prediction is that Perl 5 will stick around, and Raku is dead on arrival.

With Nim it might be the other way around: Good reasons for why new investments should go to Nim 3 rather than Nim 2, and not all that much existing investment in Nim 2. If Nim 3 sees healthy adoption, it might well be more economical to re-deploy ecosystem maintenance to Nim 3 and migrate most of the existing code, rather than keep two versions of the ecosystem going.


Replies

ghshephard • today at 5:51 PM

I know you realize this, but it is worth emphasizing that Perl 5 vs Perl 6 is a not comparable to Python 2 to Python 3. For 98%+ of code, Python 2 and Python 3 are mostly identical, and the conversion, even in massive code-bases, is completely mechanical for 99.5% of the code.

Perl 5 and Perl 6 (Raku) are different languages.