http://www.perlmonks.org?node_id=561467


in reply to Re^4: Perl is dying
in thread Perl is dying

I'll take my lumps for Everything too. The custom node inheritance and nodemethod scheme is definitely worse than Catalyst's multiple inheritance. Plus there's the fact that there have been approximately three people make any patches at all over the past three or four years... :)

Replies are listed 'Best First'.
Re^6: Perl is dying
by demerphq (Chancellor) on Jul 15, 2006 at 21:53 UTC

    Plus there's the fact that there have been approximately three people make any patches at all over the past three or four years... :)

    How many of the PM changes have you tried to merge into Everything?

    ---
    $world=~s/war/peace/g

[reply]

      None so far; the code has diverged pretty severely.

[reply]

        Diverged so far that settings no longer exist? (as an example). Our setting serialization code is about a hundred times faster than what was originally there.

        ---
        $world=~s/war/peace/g

[reply]
Re^6: Perl is dying
by waswas-fng (Curate) on Jul 17, 2006 at 16:14 UTC
    Been a while since I have posted here, Cat may not be what the OP was asking for directly, but it is evolving into something that I think will allow perl compete with the languages du jour. I don't think that perl's ability to handle text and pattern matching or other glue app usages have ever been in question, but where perl has been lacking is web based toolkits. Cat, for me, has allowed me to continue using my favorite language without having to make excuses for it. Perl 6 may or may not be a huge long term boon to our language of choice, but toolkits that allow us to compete with ruby, python, php seem like a good starting point. The point that I think is missed most of the time is that a lot of these languages or toolkits learned from the mistakes that perl made in the past and tried to smooth the bumps in the road. There is no reason we cant leap frog them in this regard.


    -Waswas
[reply]

In Section Meditations