4 ms·

For me one thing killed Perl, Perl 6. At the time when I decided to learn one of Perl, Python and Ruby as a basic text manipulating scripting language, all dis

For me one thing killed Perl, Perl 6. At the time when I decided to learn one of Perl, Python and Ruby as a basic text manipulating scripting language, all discussion of Perl revolved around how Perl 6 was not at all backwards compatable, not usable at the moment, and would replace Perl 5. Given that impression, learning Perl 5 looked like the height of stupidity.

RyanZAG 13y ago
Interestingly, this is the same thing that is currently killing Python. The lack of migration towards Python3 is causing major problems.
- Pacabel 13y ago
  There's a huge difference between Perl 6 and Python 3. And Python 3 surely is not "killing Python" or "causing major problems". In hindsight, I think it's been very good that Python 3 hasn't been about drastic, immediate change. It has been a very controlled transition that has allowed existing users to remain undisturbed, while simultaneously allowing the language to evolve. Those who don't need Python 3's benefits today are perfectly able to continue using Python 2.7. Nobody is forced into upgrading, yet Python 2 still remains very well supported. Those who want or need what Python 3 offers can upgrade when they see fit. We've seen the major libraries and frameworks support Python 3 over time, as demand for this support has grown. It now has a very robust community building around it. Unlike Perl 6, we've actually been able to seriously use Python 3 for a long time now. While it's clear now that Python 3 is the future, Python 2 users haven't been abandoned, either. Everyone has remained as good as they were before, if not better off.
Pacabel 13y ago
This is a very real phenomenon. A somewhat related one is the effect that the Perl 6 disaster has had on the reputation of the Perl community as a whole, even if Perl 5 is a very different language embraced by a different segment of the community. Unfortunately, the term "Perl" has become synonymous with terms like "failure", "incompetence" and "wheel-spinning" for a lot of people. This isn't the kind of reputation that proves useful when trying to advocate for the use of Perl 5 in new projects, for example. One will end up spending more time trying to explain that Perl 5 is pretty unrelated to Perl 6 and that its development has continued, rather than spending time explaining how it'll be beneficial to use it.
- cwyers 13y ago
  One subtle problem that I think is potentially relevant is that Classic Perl's version number has to keep incrementing from 5.x; someone who isn't following Perl development sees Perl using the same major version number as it was back in the mid-90s and assumes it's not being actively developed.

RyanZAG 13y ago

Interestingly, this is the same thing that is currently killing Python. The lack of migration towards Python3 is causing major problems.

Pacabel 13y ago
There's a huge difference between Perl 6 and Python 3. And Python 3 surely is not "killing Python" or "causing major problems". In hindsight, I think it's been very good that Python 3 hasn't been about drastic, immediate change. It has been a very controlled transition that has allowed existing users to remain undisturbed, while simultaneously allowing the language to evolve. Those who don't need Python 3's benefits today are perfectly able to continue using Python 2.7. Nobody is forced into upgrading, yet Python 2 still remains very well supported. Those who want or need what Python 3 offers can upgrade when they see fit. We've seen the major libraries and frameworks support Python 3 over time, as demand for this support has grown. It now has a very robust community building around it. Unlike Perl 6, we've actually been able to seriously use Python 3 for a long time now. While it's clear now that Python 3 is the future, Python 2 users haven't been abandoned, either. Everyone has remained as good as they were before, if not better off.

Pacabel 13y ago

This is a very real phenomenon. A somewhat related one is the effect that the Perl 6 disaster has had on the reputation of the Perl community as a whole, even if Perl 5 is a very different language embraced by a different segment of the community. Unfortunately, the term "Perl" has become synonymous with terms like "failure", "incompetence" and "wheel-spinning" for a lot of people. This isn't the kind of reputation that proves useful when trying to advocate for the use of Perl 5 in new projects, for example. One will end up spending more time trying to explain that Perl 5 is pretty unrelated to Perl 6 and that its development has continued, rather than spending time explaining how it'll be beneficial to use it.

cwyers 13y ago
One subtle problem that I think is potentially relevant is that Classic Perl's version number has to keep incrementing from 5.x; someone who isn't following Perl development sees Perl using the same major version number as it was back in the mid-90s and assumes it's not being actively developed.