2 ms·
The short answer boils down to, "It might be dangerous, you go first." Moving to a brand new language (which is what Perl 6 is, despite its long incubation and
by cwyers 10y ago
The short answer boils down to, "It might be dangerous, you go first." Moving to a brand new language (which is what Perl 6 is, despite its long incubation and its vestigal name) has real costs - the libraries you have come to depend on aren't there, new libraries to replace them aren't all written yet, some might never be, the ones that exist aren't as feature-complete and battle-tested. For a new language to get adoption, someone needs to go in there and start doing those things, and deliver a value proposition. If a language wants to get followers, at least in the beginning it's better to have one "does it better than anyone else" area than to be a jack of all trades, too.
- berntb 10y ago>> the libraries you have come to depend on aren't there See e.g. Inline::Perl5 and Inline::Python (don't know how mature that is). >> For a new language to get adoption I'm not really that knowledgeable right now, but how many weeks have Perl 6 (the language, not the libraries) had an implementation ready for production? :-) Edit: Thanks, Ulti. Close to 50 weeks. Good work of the implementors. :-)
- Ulti 10y agoSince Christmas 2015 was the "production" release of the language specification. Hence the 6.C version number, the C stands for Christmas. Rakudo around about now implements that feature set in a stable way. The last year has mostly been optimisation work in the runtime and VM. The whole thing is about as stable and production worth as Swift. That is to say features do still change, but not the ones already specced as 6.C