Show quoted text
> CHI gets a ton of benefits from Moose.
And let me assure you, I'm not trying to start a Moose war, I just love the concept of CHI (I enjoyed your talk @
YAPC about it BTW) and have seen the same basic idea implemented wonderfully without moose (e.g.
Log::Dispatch)
Show quoted text
> What do you mean by "really huge"? Do you mean amount of memory,
yes, process RSS goes up almost 12MB just using it from a quick and dirty check:
[dmuey@multivac ~]$ perl -e 'print `ps u -p $$`;'
USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND
dmuey 39922 0.0 0.0 2437344 1204 s000 R+ 1:46PM 0:00.04 perl -e print `ps u -p $$`;
[dmuey@multivac ~]$ perl -MMoose -e 'print `ps u -p $$`;'
USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND
dmuey 39928 46.9 0.2 2444940 13124 s000 R+ 1:46PM 0:00.35 perl -MMoose -e print `ps u -p $$`;
[dmuey@multivac ~]$
by comparison Log::Dispatch, that I noted earlier as a similar concept but for logging instead of caching, only
adds about 2 MB to RSS even with quite a dependency chain itself.
Show quoted text
> or amount of disk space,
not so much that
Show quoted text
> or number of dependencies,
maybe a bit: it takes time to find all of them and load them and compile them, for what benefit exactly? a few less
lines of code and MOPiness? Doesn't seem worth it to me for an abstract caching mechanism
Show quoted text
> or it just feels big conceptually?
I suppose that fits a little, MOP is cool, I get that, its a great idea. Just not when its cost outweighs the benefit.
Show quoted text
> Are you on a hosting provider with a very restricted
> amount of memory/disk space?
no, I just don't want my personal servers bogged down for no reason and our customers demand reasonable
memory use, thus Moose is out the door along w/ Java :)