[Chicago-talk] I want to evangelize

[Jim Thomason]

Okay, I've got Basset up on CPAN. IMESHO, it kicks a lot of ass, and
I'm quite proud of it. However, my pride in my work does not
necessarily translate into other people wanting to use it.

"Oh, look at wacky Jim and his wacky little hobby project. Time for real work."

I hate that attitude (and yes, I have encountered it). But I don't
necessarily know what would convince people to try it out, kick the
tires, and run with it.

So I'm opening it up to you guys. What sort of things would you all
want to see in a software product before you'd consider it?
Documentation? Examples? Speed tests? Preaching? Honestly, would
anything convince you to look at it? (I'm not being critical or
anything, just speaking generally - we all tend to get set in our ways
with things, so I know I have an uphill fight).

This is my standard issue with my software - since I know it so
intimately, I don't necessarily know where to begin. To me, it's
obvious. What would convince you?

-Jim...