Object framework for a *::Tiny module

zby has asked for the wisdom of the Perl Monks concerning the following question:

I know there can never be an ultimate and objective answer for this question - but at least I hope to learn what is the popular choice here. I cannot decide myself what to choose for WebNano so please help me. The important point is that I try to subscribe to the ::Tiny way of doing things with this module so this question is really a poll aimed at people that care for these kind of modules.

Right now I am hesitating between Any::Moose and Class::XSAccessors with the following pros and cons.

Pro Any::Moose

Possibly no XS
Can mean Moose for those that like to use Moose extended features

Pro Class::XSAccessors

Very fast
Small
With MooseX::NonMoose can also be extended to Moose with no hassle at all
Used by Alias

What do you think?

Comment on Object framework for a *::Tiny module

Replies are listed 'Best First'.
Re: Object framework for a *::Tiny module by DrHyde (Prior) on May 20, 2010 at 10:07 UTC
If you want to be ::Tiny, you shouldn't use either of 'em. See http://www.nntp.perl.org/group/perl.datetime/2007/01/msg6584.html.	[reply]
Re^2: Object framework for a *::Tiny module by zby (Vicar) on May 21, 2010 at 09:38 UTC
Thanks - that was informative. But I think I cannot afford this level of ::Tiny, it's more in the direction of ::Tiny as much as I can, but not really entering the competition :) For my defence Template::Tiny is neither completely dependencies free.	[reply]
Re: Object framework for a *::Tiny module by ctilmes (Vicar) on May 19, 2010 at 21:02 UTC
Object::Simple because it is, well, simple. It fits in well with the ::Tiny model you are looking for.	[reply]
Re: Object framework for a *::Tiny module by BioLion (Curate) on May 20, 2010 at 11:47 UTC
This is probably a naive question, but does Tiny (maximal code usage density?) bear any relation to Lite (minimal memory load?)? Does one come at the expense of the other? I only ask because generally I work to Lite principals, because I am usually memory limited rather than processor limited, however my code usually ends up pretty minimal too, so i am just wondering if this is just me, or whether the two themes are related? I should add that I don't check my code usage usually, and though I try to pack in functionality, I am aware that small doesn't always equal beautiful... Just a something something...	[reply]
Re^2: Object framework for a *::Tiny module by zby (Vicar) on May 21, 2010 at 09:41 UTC
Interesting question - I would like to see some discussion about it between the more knowledgeable than me :) Maybe you could ask that question at Alias's blog?	[reply]