Just a passing observation from someone who used to write Perl, used Perl in his term papers, and had one of his first ever job interviews for a Perl-related position. For me personally, the...
Just a passing observation from someone who used to write Perl, used Perl in his term papers, and had one of his first ever job interviews for a Perl-related position.
For me personally, the reason why I don't consider learning Perl 6 has nothing to do with “the legacy” of Perl or with the long development time. It has everything to do with the fact that, after being scarred—among other dynamic-typing-related things—by the few months where I had to support a medium-large medium-shit Ruby-On-Rails codebase alone, I have decidedly moved on to the “boring”, statically-typed languages.
And, before any of you monks will start typing (heh), I know that Perl 6/Raku/Camelia has gradual typing or something like that, but gradual typing is just completely missing the point (again, IMHO). Any language is amazing when you're the only programmer, but given enough time, sub-par colleagues, and a lacking code-review culture, all code turns to shit. The strictness of the language is simply a protective measure, which slows down the descent. And which you don't really need when you have great colleagues and high-quality culture. But something tells me that that is not a situation present in the majority of tech companies.
(Edited to make it clearer that the ROR project wasn't the only thing, but merely the last straw.)
Just a passing observation from someone who used to write Perl, used Perl in his term papers, and had one of his first ever job interviews for a Perl-related position.
For me personally, the reason why I don't consider learning Perl 6 has nothing to do with “the legacy” of Perl or with the long development time. It has everything to do with the fact that, after being scarred—among other dynamic-typing-related things—by the few months where I had to support a medium-large medium-shit Ruby-On-Rails codebase alone, I have decidedly moved on to the “boring”, statically-typed languages.
And, before any of you monks will start typing (heh), I know that Perl 6/Raku/Camelia has gradual typing or something like that, but gradual typing is just completely missing the point (again, IMHO). Any language is amazing when you're the only programmer, but given enough time, sub-par colleagues, and a lacking code-review culture, all code turns to shit. The strictness of the language is simply a protective measure, which slows down the descent. And which you don't really need when you have great colleagues and high-quality culture. But something tells me that that is not a situation present in the majority of tech companies.
(Edited to make it clearer that the ROR project wasn't the only thing, but merely the last straw.)