Re: [RANT] Should we try to keep compatibility with old perl5s?

2018-08-12 Thread Shlomi Fish
Hi Lars, thanks for your comprehensive and informative reply. On Sun, 12 Aug 2018 10:23:50 +0200 Lars Dɪᴇᴄᴋᴏᴡ 迪拉斯 wrote: > I have read the posts linked in your message. > > > should I as a CPAN author/maintainer/adopter accommodate for people > > running old perl5s > > It's your choice.

Re: [RANT] Should we try to keep compatibility with old perl5s?

2018-08-12 Thread Arthur Corliss
On Sat, 11 Aug 2018, Shlomi Fish wrote: Hi all! This post is a little flamebait, so please try to keep the discussion civil. Anyway, after reading the discussion in this public github issue, and following some of the links (especially

Re: [RANT] Should we try to keep compatibility with old perl5s?

2018-08-12 Thread Linda A. Walsh
Shlomi Fish wrote: Hi all! do you think I was being unreasonable, or should I as a CPAN author/maintainer/adopter accommodate for people running old perl5s, in my case 5.10.x and below: Going backwards it becomes more difficult to support an old version, along with older versions having

Re: [RANT] Should we try to keep compatibility with old perl5s?

2018-08-12 Thread Xavier Noria
I’ve been out of the Perl community for many years, but to give you an example of the opposite trend, in Rails we drop support for old Ruby really fast. People need to move forward if they want to upgrade Rails (and culturally, they normally do). Giving this example to subscribe something already

Re: [RANT] Should we try to keep compatibility with old perl5s?

2018-08-12 Thread Shawn H Corey
On Sun, 12 Aug 2018 13:41:54 +0200 Xavier Noria wrote: > I’ve been out of the Perl community for many years, but to give you an > example of the opposite trend, in Rails we drop support for old Ruby > really fast. People need to move forward if they want to upgrade > Rails (and culturally, they

Re: [RANT] Should we try to keep compatibility with old perl5s?

2018-08-12 Thread Shlomi Fish
Hi, On Sun, 12 Aug 2018 09:33:59 +0100 Stephen Patterson wrote: > Hi Shlomi > > It's been several years since I was last active in the Perl community, so > take this with a good pinch of salt (I think 5.8 was new at the time) :) > > That being said, I remember each module having a

Re: [RANT] Should we try to keep compatibility with old perl5s?

2018-08-12 Thread Dan Book
On Sat, Aug 11, 2018 at 4:39 PM Shlomi Fish wrote: > Hi all! > > This post is a little flamebait, so please try to keep the discussion > civil. > > Anyway, after reading the discussion in this public github issue, and > following > some of the links (especially > >

Re: [RANT] Should we try to keep compatibility with old perl5s?

2018-08-12 Thread Paul Bennett
I have faced this question head-on with some of my modules. My take is that there are many, many corporations version-locked to specific "enterprise-grade" Linux distros, and stuck with system Perls maybe as old as 5.10, and potentially stuck with security policies that make solutions like

Re: [RANT] Should we try to keep compatibility with old perl5s?

2018-08-12 Thread Lars Dɪᴇᴄᴋᴏᴡ 迪拉斯
I have read the posts linked in your message. > should I as a CPAN author/maintainer/adopter accommodate for people > running old perl5s It's your choice. You are in charge of the software, so you get to decide. I'm certain that's how it's been generally handled in past, too. Are you asking to

Re: [RANT] Should we try to keep compatibility with old perl5s?

2018-08-12 Thread Stephen Patterson
Hi Shlomi It's been several years since I was last active in the Perl community, so take this with a good pinch of salt (I think 5.8 was new at the time) :) That being said, I remember each module having a dependencies file with the minimum compatible perl version for that version of the module,

Re: [RANT] Should we try to keep compatibility with old perl5s?

2018-08-12 Thread Shlomi Fish
On Sun, 12 Aug 2018 13:41:54 +0200 Xavier Noria wrote: > I’ve been out of the Perl community for many years, but to give you an > example of the opposite trend, in Rails we drop support for old Ruby really > fast. People need to move forward if they want to upgrade Rails (and > culturally, they