News for hackers. Stuff that matters.

A comment on The Future of Perl. Parent comment

Re:The Future of Perl by forgotmypw17 on Wednesday March 24, 2021 @09:25AM (#26566873)
It is already modern. The Perl community has boldly remained committed to compatibility over chasing the shiny and breaking shit, unlike many others (coughphpcough), which is why I chose Perl for a new project a couple years ago.

I don't WANT so-called modernization. I want my program to remain working without having to change. it

[ Parent | on HN ]
Re:The Future of Perl by klibertp on Wednesday March 24, 2021 @10:06AM (#26567363)
> I want my program to remain working without having to change. it

Can't you bundle the interpreter, possibly stripped down and compiled as a static binary, along with your program?

But yes, strict backward compatibility, while having many downsides, provides a lot of value, too. The trade-off is situation and project dependent, and it's good to have both kinds of platforms: ones solid as a rock and moving slowly, and ones moving fast and breaking things.

[ Parent | on HN ]
Re:The Future of Perl by bmn__ on Wednesday March 24, 2021 @12:32PM (#26569435)
https://metacpan.org/pod/pp https://metacpan.org/pod/staticperl https://metacpan.org/pod/perlcc

But that's the worst way to deploy a program.

[ Parent | on HN ]
Re:The Future of Perl by jrsj on Wednesday March 24, 2021 @11:10AM (#26568204)
This will work for awhile until you stop receiving security updates and have to adapt to breaking changes to do so.
[ Parent | on HN ]
Re:The Future of Perl by forgotmypw17 on Wednesday March 24, 2021 @12:06PM (#26569038)
Bundling the interpreter would interfere significantly with being able to download and run from source.
[ Parent | on HN ]