Maybe the fact that nobody has voted on Spiffy yet could be a warning sign?
It could also be a sign that the module is relatively new, and/or that people don't vote much anyway (Class::Accessor has 1 vote, for instance)
To me, Spiffy is yet another way of being too clever for your own good
I must confess I feel slightly uneasy about a module that uses Exporter, OO and source filters at the same time, but OTOH it's trying to solve a couple of fairly basic (as in "hard to solve") issues with the perl OO mechanism. Whether these issues need solving is ofcourse debateble.
If cleverness alone would be a problem, people wouldn't use Class::DBI::Loader either. It all depends on the problem you're trying to solve. If you want full control and performance, you use DBI directly. If you want to quickly write some code to edit a couple of tables in a database and performance isn't your primary concern, Class::DBI::Loader might be perfect for you.
I wouldn't use Spiffy for anything large at the moment (it looks almost impossible to remove after you've put it in your code, which can be a big problem if it doesn't work as well as you expected), but using it in a smaller project should be interesting, and might also give more insight into Spiffy's (dis)advantages. I'd welcome a couple of reviews :-)
updated: punctuation.
In reply to Re^2: Wanted: Spiffy evangelist
by Joost
in thread Wanted: Spiffy evangelist
by grantm
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |