Beefy Boxes and Bandwidth Generously Provided by pair Networks
Welcome to the Monastery
 
PerlMonks  

Re^15: What esteemed monks think about changes necessary/desirable in Perl 7 outside of OO staff (don't feed)

by likbez (Sexton)
on Oct 02, 2020 at 02:37 UTC ( [id://11122463]=note: print w/replies, xml ) Need Help??


in reply to Re^14: What esteemed monks think about changes necessary/desirable in Perl 7 outside of OO staff (don't feed)
in thread What esteemed monks think about changes necessary/desirable in Perl 7 outside of OO staff

This node falls below the community's threshold of quality. You may see it by logging in.
  • Comment on Re^15: What esteemed monks think about changes necessary/desirable in Perl 7 outside of OO staff (don't feed)
  • Download Code

Replies are listed 'Best First'.
Re^16: What esteemed monks think about changes necessary/desirable in Perl 7 outside of OO staff (don't feed)
by GrandFather (Saint) on Oct 02, 2020 at 03:42 UTC

    Perl 6 derailed the natural versioning evolution of Perl so the change to version 7 is really just a just regularizing the situation and is justified by that standard alone. Without the Perl 6 influence Perl 5 would have evolved into Perl 6 long ago - perhaps around Perl 5.10? I don't think there needs to be further justification for the version number change and for taking the opportunity to slip in few breaking changes that reflect about 20 years of best practice.

    There is nothing wrong with challenging the status quo and suggesting improvements. Where this thread has come unstuck is in a small number of cases very common Perl idiom has been challenged with the suggestion that such practices should be abandoned. That tweaks a major nerve as most of those facilities in Perl are why many of us love the language. Removing or crippling post fix statements for example would break much more code than making strictures the default.

    It is refreshing to hear that we are regarded as zealots. That is a validation of our passion for Perl and that we care what happens to the language. There is life in that puppy yet.

    Optimising for fewest key strokes only makes sense transmitting to Pluto or beyond
Re^16: What esteemed monks think about changes necessary/desirable in Perl 7 outside of OO staff (don't feed)
by hippo (Bishop) on Oct 02, 2020 at 09:17 UTC
    FORTRAN after 1977 adopted 11 years cycle for new versions

    I'm sorry to say that this assertion is utterly without basis. Here are the release dates of the Fortran versions post-77:

    VersionYear of releaseYears since previous release
    Fortran 90199214
    Fortran 9519964
    Fortran 200320048
    Fortran 200820106
    Fortran 2018201810
    Should it be possible on perlmonks to criticize some aspects of Perl 5 current features and implementation as well as its use without being denigrated as a reward?

    Sure, criticize away. However, everyone else is also free to criticize your criticism. And when your criticism contains glaring factual errors such as your assertion about the Fortran release cycle then that somewhat undermines the credibility of the rest of your arguments.

    Here endeth the feeding.


    🦛

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://11122463]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others musing on the Monastery: (4)
As of 2024-04-23 15:19 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found