in reply to Re^7: The Future of Perl 5
in thread The Future of Perl 5

You guys keep quarreling about the past while we need a strategy for the future.

Cheers Rolf
(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery FootballPerl is like chess, only without the dice

Replies are listed 'Best First'.
Re^9: The Future of Perl 5
by zentara (Cardinal) on Aug 22, 2018 at 16:05 UTC
    Maybe Perl5 will follow in the footsteps of COBOL. 20 years from now, high pay will go to the few programmers who can still repair/update Perl5 legacy code. :-)
    I'm not really a human, but I play one on earth. ..... an animated JAPH
[reply]
      Probably...

      So what's the salary of TCL experts nowadays? :)

      Cheers Rolf
      (addicted to the Perl Programming Language :)
      Wikisyntax for the Monastery FootballPerl is like chess, only without the dice

[reply]
[reply]
Re^9: The Future of Perl 5
by chromatic (Archbishop) on Aug 22, 2018 at 16:57 UTC
    we need a strategy for the future

    You're right! I'd like that strategy not to repeat the mistakes of the past.

    For example, I think we should collectively acknowledge that deliberate fragmentation, in the hope that we'll have eventual convergence, has rarely worked for us. Experimenting with multiple competing object systems on the CPAN and hoping eventually something will get into the core has left us with a core that's (apart from mro and parent) unchanged since 5.004 or so for objects with any sizable CPAN dependency chain pulling in multiple competing object systems.

[reply]
[d/l]
[select]

      That sounds more like, “I want you all to admit you were wrong,” than it sounds like a strategy leading to any action items. It also sounds like retconning strongly against the grain of what the CPAN is; an uncurated collection, not a collective or even its gentrified cousin, a democracy.

[reply]

        Hm. Well then let me rephrase.

        I'd like this "experiment in the CPAN to figure out what can eventually go in the core" to have a better defined process with an explicit step that encourages consolidation. Look at exception handling, for example: Try::Tiny exists and works (and has a few alternatives) but eventually helped get core exception handling improvements such that it's no longer required for correct behavior.

[reply]

In Section Meditations