in reply to Re^4: Moose or Mouse for production use
in thread Moose or Mouse for production use

I may have exactly what you are looking for. Ovid has a series of blog articles about his attempts to solve some of the inheritance tangles at the BBC. Here they are in order. Pictures of the class hierarchy in question. Initial thoughts on how roles might help. Then he ran into an interesting technical issue. More thoughts on refactoring using Moose roles. Then roles start to pay off for him. Then more on why this is good.

This gives you a sense of how migrating to Moose worked out for a good programmer on a realistically complex code base. Better yet, he describes exactly why it was helpful for him, and you get to see both the positives and negatives with a timeline to indicate how much of an investment this was.

Speaking personally my reaction was, "I'd rather work on a small code base without all of that complexity." But if I had to work in a larger code base, I'd definitely investigate whether Moose could clean things up.

  • Comment on Re^5: Moose or Mouse for production use

Replies are listed 'Best First'.
Re^6: Moose or Mouse for production use
by BrowserUk (Patriarch) on Apr 02, 2009 at 07:42 UTC