zlacker

[return to "What Killed Perl?"]
1. orev+kg1[view] [source] 2025-11-19 18:08:42
>>speckx+(OP)
The backwards incompatibility of Perl 6 absolutely killed Perl.

There are many languages still in use today that have all kinds of warts and ugliness, but they remain in use because they still have momentum and lots of legacy things built in them. So being ugly or old isn’t enough of a factor for people to abandon something in droves.

Once you need to rewrite everything, there’s no reason to stay with something you know since you need to fully retool anyway.

As a Perl programmer since v5 was released, the confusion around 6 completely destroyed almost everyone’s enthusiasm, and immediately caused all new projects to avoid Perl. It seemed like 5 had reached the end of the line, and 6 was nowhere to be found. Nobody wants to gamble so many hours of their lives, and the future of their business, on such an uncertain environment.

If Perl 6 had any visible movement within the first few years, it might have survived, but it was a good decade before they even admitted Perl 6 might take longer than expected, and then more time after that before they admitted it should have been a new language. 6 was interesting for language geeks, and they probably did some cool things, but you can’t run a large popular project like it’s a small research project. That completely destroyed all momentum in the community. Perl 5 development only resumed far too late, after the writing was already on the wall.

Both Bill Gates and Linus understand backwards compatibility as a sacrosanct principle. Python only just barely survived the jump from 2 to 3. JavaScript can only survive this because there’s no other option in a browser.

◧◩
2. kaashi+5o1[view] [source] 2025-11-19 18:37:30
>>orev+kg1
> Python only just barely survived the jump from 2 to 3.

I really don't think this is true at all.

Python 2 to 3 took a really long time, it was a real struggle, lots of people stayed on 2 for a really long time.

But I really don't think Python was close to dying the same way Perl has/is. There was no risk of Python not "surviving" in my opinion.

There was always a clear way forward and people were actually moving. The mass migration of millions or billions of lines of code from 2 to 3 actually happened and has many high profile million+ line migrations, like Yelp or Dropbox.

There was never anything similar for Perl 5 to 6, totally different situation.

◧◩◪
3. foofoo+Dw1[view] [source] 2025-11-19 19:16:21
>>kaashi+5o1
> I really don't think Python was close to dying

It absolutely was. What saved it was:

1. The data science / AI crowd that was gathering momentum any many only used Python 3.

2. No popular alternative. Perl got python as an alternative.

Python was also a good, simple language and had a good healthy culture. But it's nothing sort of a miracle that it survived that biblical software calamity.

◧◩◪◨
4. tptace+cG1[view] [source] 2025-11-19 20:01:35
>>foofoo+Dw1
Long before the AI/data science breakout, we were noticing in our consulting practice (2016-2020) a sharp dropoff in Ruby at startups, and Python as the modal language (by the time I left in 2020, it would have gone Python -> Node -> Ruby).

So no, I don't think AI saved Python; it was fine before then.

◧◩◪◨⬒
5. smohar+jV1[view] [source] 2025-11-19 21:14:40
>>tptace+cG1
2016 already puts one far into the AI explosion. The current hype cycle, with LLMs as a service at the forefront, arguably makes python less relevant than in it was in the mid 2010’s. The current crop of “AI Engineers” can use whatever languages they want for the most part. In 2016 most practitioners were leveraging a lot more of the standard scientific computing frameworks afforded by python.
[go to top]