A comยญment on the Medium verยญsion of last weekโ€™s artiยญcle got to me:

I wish theyโ€™d just leave Perl staยญtยญic. Then we wouldnโ€™t have to waste monยญey retestยญing legaยญcy Perl apps on the newest verยญsion every couยญple of years, in case new feaยญtures we donโ€™t want breaks code thatโ€™s been unchanged for years. [โ€ฆ] Sometimes things should just be left to die gracefully.

William Smith

Programming lanยญguages, like all softยญware, change to meet new chalยญlenges. Developers add new feaยญture enhanceยญments, users find bugs for them to fix, and occaยญsionยญal design errors need to be corยญrectยญed. In Perlโ€™s case, the Perl 5 Porters (the group of volยญunยญteers that develยญop and mainยญtain Perl) have had an explicยญit backยญward comยญpatยญiยญbilยญiยญty and depยญreยญcaยญtion polยญiยญcy since 2011 that tries to proยญtect the Perl user comยญmuยญniยญty from the breakยญage of old code while still movยญing the lanยญguage forยญward. In short, they do their absolute best to minยญiยญmize your testยญing and changes.

To that end, the Perl develยญopยญers have done an amazยญing job preยญsentยญing new synยญtacยญtiยญcal feaยญtures as only enabled when adding the approยญpriยญate use feature or use VERSION conยญstruct. If you do not add this code, the new synยญtax will not be enabled and your legaยญcy code will not break. Incompatible changes, if there are any, are always docยญuยญmentยญed in a releaseโ€™s perldelta docยญuยญment (hint: itโ€™s under the headยญing โ€‹โ€œIncompatible Changesโ€).

Given all this, it is a monยญstrous thing to demand an entire volยญunยญteer comยญmuยญniยญty stop enhancยญing their platยญform so that your parยญticยญuยญlar appliยญcaยญtions can remain staยญtยญic while conยญtinยญuยญing to take advanยญtage of the supยญport polยญiยญcy genยญerยญousยญly offered for recent releasยญes. If you need an unchangยญing platยญform, donโ€™t upgrade itโ€”and take all the responยญsiยญbilยญiยญty that implies, such as the backยญportยญing of secuยญriยญty fixยญes beyond the three-โ€‹year supยญport comยญmitยญment offered (again, gratis) by Perlโ€™s developers.

You have no right to demand Perl stands still and โ€‹โ€œdies graceยญfulยญlyโ€ any more than anyยญone has the right to demand that of you.

21 thoughts on “Should Perl die gracefully?

  1. [โ€ฆ] Rememยญber that conยญsisยญtenยญcy builds trust from your audiยญence. Make time to write regยญuยญlarยญly and pubยญlish posts as often as you can manยญage. I set a goal to pubยญlish at least once a week and have kept up this pace since Janยญuยญary of this year. You can often find new topยญics as you monยญiยญtor and parยญticยญiยญpate in the social forums in which youโ€™re proยญmotยญing your blog, espeยญcialยญly in the comยญments. Even negยญaยญtive comยญments can driยญve new topics. [โ€ฆ]

Comments are closed.

Mentions