Beefy Boxes and Bandwidth Generously Provided by pair Networks
Don't ask to ask, just ask
 
PerlMonks  

Re^2: The Corinna RFC for getting modern OO into the Perl core is taking shape

by haj (Vicar)
on Aug 20, 2021 at 11:58 UTC ( [id://11135984]=note: print w/replies, xml ) Need Help??


in reply to Re: The Corinna RFC for getting modern OO into the Perl core is taking shape
in thread The Corinna RFC for getting modern OO into the Perl core is taking shape

Will development or maintenance of them cease? Will vast swathes of code have to be rewritten as those modules become unmaintained?

That's a question for the current maintainers of all these modules to answer, and if they don't want to continue maintaining their modules, to the user base. Modules have become unmaintained for a variety of reasons, and "it's now in the core" is not the most frequent one. If no volunteer is found to step in, then it will still take some years until users must rewrite their code since Perl will always value compatibility.

And also, it's a loooong way. The first version of Corinna lacks a lot of features which have been added to e.g. Moose or Moo.

Either way I hope the decision to include any such system in the language itself is not one which we shall come to regret down the line.

We might regret it if we have the expectation that someone else will, without us paying for that, maintain the modules we want forever. But I hope that we are not like that, otherwise I'd say: we deserve no better.

Replies are listed 'Best First'.
Re^3: The Corinna RFC for getting modern OO into the Perl core is taking shape
by hippo (Bishop) on Aug 20, 2021 at 12:32 UTC

    It is indeed a long way off. I am still frequently seeing production environments today using 5.16 and occasionally some as far back as 5.8 so there won't be universal coverage of any to-be-introduced language features for well over a decade after release. The consequences of the decision may not be seen for a long time but once the decision is made it will be very difficult to avert them entirely.

    I'm sure that none of us have the expectation of perpetually maintained modules forever, gratis. My concern is that the incentive to maintain an already-widely-used module will likely be reduced if the language is extended to include some/most of the functionality.

    The first version of Corinna lacks a lot of features which have been added to e.g. Moose or Moo.

    Intentionally so - the docs make a big noise about it being an MVP. Perhaps that is all it will ever be: such that to do anything beyond that minimum would require one of the already extant alternatives. That might just be the best of all outcomes.


    🦛

Log In?
Username:
Password:

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

How do I use this?Last hourOther CB clients
Other Users?
Others chilling in the Monastery: (6)
As of 2024-03-28 11:50 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found