zlacker

>>lumpa+(OP)
I don't want a community - I want a programming language. Preferably one that doesn't throw away billions of lines of existing code just because.

>>musica+ji1
There are countless dead programming languages without communities you can pick then.

>>doesnt+Ri1
Ruby and Perl are great examples of massively popular languages that withered because the language/platform outpaced the community.

If the first question you’re asking yourself looking at a code base is “what version is this/do I know this version” then that language is not facilitating you.

The successful languages are ones where “the community” prioritises backward compatibility. Java, C, Python have backward compatibility spanning decades. There’s a few discontinuities (lambdas in Java 8, Python 3, C++) but in most cases there’s a clear mapping back to the original. Python 3 is an exception to this but the migration window was something like 15 years…

Busy engineers, scientists and academics have little interest in keeping up to date with language features. A computer and a programming language are a tool for a job and the source code is just an intermediate artifact. These are your “community”, and the stakeholders in your success.

>>rusk+Tj1
Perl have almost perfect backward compatibility, but small community and bad renown are not so good.

>>melago+so1
Perl doesn't have "perfect backward compatibility" in the normal sense of the word. There is only Perl 5 which is perfectly compatible since it hasn't changed for 25+ years (which is how they achieved "compatibility" -- by not changing), and there's Perl 6 which isn't backward compatible and nobody really uses it.

>>hnfong+nu1
> Perl 5 ... hasn't changed for 25+ years.

A major new version of Perl ships regularly. A few weeks ago the latest major new version shipped. From the 2025 changes document:

> Perl 5.42.0 represents approximately 13 months of development since Perl 5.40.0 and contains approximately 280,000 lines of changes across 1,600 files from 65 authors.

Skipping back 5 major new versions (to 2020):

> Perl 5.32.0 represents approximately 13 months of development since Perl 5.30.0 and contains approximately 220,000 lines of changes across 1,800 files from 89 authors.

2015:

> Perl 5.22.0 represents approximately 12 months of development since Perl 5.20.0 and contains approximately 590,000 lines of changes across 2,400 files from 94 authors.

2010:

> Perl 5.16.0 represents approximately 12 months of development since Perl 5.14.0 and contains approximately 590,000 lines of changes across 2,500 files from 139 authors.

There's been well over 10 million lines of code changed in just the core Perl codebase over the last 25 years reflecting huge changes in Perl.

----

Perl 6 ... isn't backward compatible

Raku runs around 80% of CPAN (Perl modules), including ones that use XS (poking into the guts of the Perl 5 binary) without requiring any change whatsoever.

(The remaining 20% are so Perl 5 specific as to be meaningless in Raku. For example, source filters which convert Perl 5 code into different Perl 5 code.)

----

But you are right about one thing; no one you know cares about backwards compatibility, otherwise you'd know the difference between what you think you know, and what is actually true.

>>raiph+P14
> But you are right about one thing; no one you know cares about backwards compatibility, otherwise you'd know the difference between what you think you know, and what is actually true.

What the hell is this? Even if nobody I know cares about backwards compatibility, how does this relate to whether my knowledge is true or not?

Apologies for trivializing perl5's progress in the past 25 years, but come on, chill out dude.