It entirely depends on how you use Moose on whether or not things are "slow." Create lots of objects and mutate their accessors traditionally via hash keys? Moose might be slow in comparison. Are your objects mostly immutable and long lived? Moose might not be a problem.
When I see posts like this, I always have a ton of questions: Why do you want to introduce Moose into your code base? Does it really make sense to do so? Are you introducing too much cognitive load for your colleagues by introducing new technology? Will they have to maintain and extend this code? The power in Moose is about development speed and the ability to quickly model a system with proper constraints, not necessarily performance. If those things aren't important to you or if the hassle of bringing your organization into the 21st century is too great, I seriously question your choice. I know you came here asking about speed, but I think that is the wrong question. Ultimately Moose is a tool. And if your team isn't effective in absorbing new technology, don't do it without a lot of consideration. On Sun, 29 Jun 2014 13:14:51 +0530 Manoj Shekhawat <manoj7shekha...@gmail.com> wrote: > Hi Geeks, > > Can you please give me proper justification that Moose isn't that > slow, many people in my organisation are resisting its usage by just > saying that it's slow. > > I know we can increase it's speed by using: > > __PACKAGE__->meta->make_immutable; > > But any other points will be very helpful, we in our organization are > deciding to build a new automation tool using Moose. > > Thanks in advance!! > -- Nicholas Perez XMPP/Email: n...@nickandperla.net https://metacpan.org/author/NPEREZ http://github.com/nperez
