Re^2: Should I come back to Perl?

\o,

> "The applications you write today in Perl 5 will still be capable of running in Perl 5 in a decade. A minor update here and there may be necessary, but they will still be runnable."

Sure, but I'm an Open Source guy. I want other people than me to run my software too ... and this might be hard at some point. Technically, every program ever written is still runnable, but the effort might increase over the years.

The shebang line is a questionable indicator though, given that Python might alias as python2, python3, python27, ... while Perl is usually perl, right?

I admit that CPAN is about three times as large as Python's PyPi is. I just hope that there won't be a version conflict between the Perl versions. Perl6 has its own CPAN, right?

Regards and all that,
jkl

Comment on Re^2: Should I come back to Perl?

Replies are listed 'Best First'.
Re^3: Should I come back to Perl? by Your Mother (Archbishop) on Sep 11, 2015 at 17:05 UTC
Everyone keeps telling you to ignore Perl6. Perl5 has done an excellent job with backwards compatibility and introducing new features and deprecating old ones in the right ways. Half the code in the codebase I'm paid to work on is from 1998. Ran on 5.4.0 seventeen years ago. Runs fine now. I have total confidence it will run fine on Perl 5.30.0 in eight years.	[reply]
Re^3: Should I come back to Perl? by Anonymous Monk on Sep 11, 2015 at 16:57 UTC
"The applications you write today in Perl 5 will still be capable of running in Perl 5 in a decade. A minor update here and there may be necessary, but they will still be runnable." Sure, but I'm an Open Source guy. I want other people than me to run my software too ... and this might be hard at some point. Technically, every program ever written is still runnable, but the effort might increase over the years. This is a straw man argument. I don't see Anonymous Monk suggesting that nobody would be maintaining your project in ten years. Any piece of software that is around and being used in ten years will have had updates by some maintainer along the way. The other fallacy in this reasoning is that it seems to assume applications written in other languages won't need to follow similar maintenance paths. I assure you that if you write an application today in any live programming language, if it's still in broad use ten years from today, it will have had updates somewhere along the way. Most code cleanly written in Perl 5 ten years ago would require no changes to run in Perl 5 now. There are a few exceptions for code that used pseudo-hashes, or `$*`, among a few other things. And unclean code that was depending on hash ordering would fail, but that was documented ten years ago to be a bad practice. That is actually a better situation than code written ten years ago in many other languages. Perl 5 has done a better job of maintaining backwards compatibility than most other actively developed languages. And I see no reason to believe that trend wouldn't continue into the future. If you don't want to come back to Perl 5, don't. But it would be silly to eschew Perl 5 out of fear of events that nobody can predict. If it is a good language for getting things done right now, use it. It's not like you're going to be able to count on Ruby being included with Linux in ten years, or five, or 1. Perl, yes for 1, and five, and probably for ten.	[reply] [d/l]
Re^4: Should I come back to Perl? by jekyll (Acolyte) on Sep 11, 2015 at 19:13 UTC
\o, thank you! (And sorry if I act like I don't really want to be here. That's not true.) Guess I'll start Perl'ing tomorrow again then. :-) Regards and all that, jkl	[reply]