Re^3: Perl is dying

[chromatic]

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

The last time I looked at it, it had almost no usable documentation, a weird development process that made a lot of existing software obsolete very quickly, and some design decisions that frightened me. That was several months ago; I haven't had time to look again.

It's also not a replacement for mod_php, which is what I believe the original poster wanted.

[castaway]

.. Says a man who's worked on the internals of Everything, which at first glance also seems like a real crazy idea :)

Certainly the documentation has improved 100-fold in the last few months, the newest version had docs as its big goal. As for the dev process, I'd appreciate if you'd qualify that remark, preferably on the mailing list where the core devs can answer your concerns.

Can't say I have a clue about mod_php though.. If its "html pages with code in", nope, Catalyst doesn't replace that. Although one can use a PHP view :)

C.

[chromatic]

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... :)

[demerphq]

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?

[waswas-fng]

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.

[Aristotle]

How is Anything coming along? ;)

[castaway]

Waiting on some fairly remotely related yak shaving.. which is waiting on some other things.. etc. etc. See blog post.

And actually I've been playing Might & Magic VII instead lately ;)

C.

[zby]

The development of Catalyst was moving fast and I think this was a good trade off for documentation and API stabillity at this stage of development. I know you can use this reasoning as an excuse for every project and I don't have any ready theory here - but for sure it depends on the size of the project and Catalyst being quit a big one needs some more time in the 'rapid prototyping' phase. Now the documentation is improving and I believe the API is quite backward compatible.