I don't think any relies on __PACKAGE__, it's just a nice syntactic way to make your code easier to repurpose; package name change doesn't require change in code. Cutting and pasting a declaration means you only edit the params, not the package name.
I've thought about how much PerlMonks could gain rewritten in Catalyst. Do *not* get me wrong. I love this place, I adore the monks who care for it and totally appreciate their service (Gods, Janitors, Dev, all). That said, this is easily the slowest site I ever visit. I don't mind -- I remember what modem speeds were like in the 90s and I still feel spoiled on any modern connection -- but I'd certainly enjoy a speed-up. http://www.everydevel.com/ just timed out, for example.
Consider how many people it takes to make this place run and add features. How much legacy cruft is in the guts. The power of Catalyst, which does come with some bulk, is that one developer can replace a team, just about any deployment is possible, and if you don't like DBIC you can use Rose::DB or DBI or MyCrazyWheelIdidntKnowWouldBeSoHardToDoRightx.
(Though I have been curious what a Catalyst rewrite in Moose might look like...)
In reply to Re: The New Everything
by Your Mother
in thread The New Everything
by atemerev
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |