I find that learning new tools gives me perspective on why I do things the way I do. Sometimes the new techniques and technologies get integrated into my day to day tool-set, sometimes they don't. It depends on what the New Thing makes easier, simpler, or possible.
I learned CGI when I was confronted with creating more than a single static web-page; CGI::Fast when I started running up against the performance wall with CGI. I learned mod_perl of necessity when I started a contract at a site the used it in preference to CGI::Fast.
I looked at the 'inside-out' object formalism when it came out and adopted it for a home-project before deciding that it was really over-kill for what I was doing. Abigail II and I had a couple of spirited debates (in both senses -- lively and we were both drinking beer at the time) about the techniques culminating an an agreement that I'd try inside-out on a live (paying contract) some time and report back.
I consider Moose and Catalyst in the same light. They are different ways to approach my basic problem: how do I apply my knowledge and tool-set toward solving a 'Problem in the Real World'. That is, after all, what I am paid to do.
Knowing about Moose or Catalyst increases my store of knowledge and adds to the number of problem solving techniques in my arsenal. The more different techniques I have at my disposal for sorting my Client's Problem, the better my chances for building them a good solution, on time and under budget. (Which is also what I'm paid for.)
----
I Go Back to Sleep, Now.
OGB
In reply to Re: Should I learn Moose
by Old_Gray_Bear
in thread Should I learn Moose
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |