Question to developers...
When you release a new program what makes you decide to release it as
freeware as opposed to shareware and vice versa?
I'm a 'once in a while' programmer now. I coded for a living from the mid
'70s through the late '80s and decided I'd had enough with trying to make
the tool that satisfied every bosses desire. "I like that, but what do you
think about adding ...." get real old, real quick! Especially when we went
into most of what I wrote with design specs and specific targets.
Wrote some stuff in 6502 assembler - commercial products - and even though
they paid me for the time I put into them I found out soon enough that the
public was worse to work for than the corporate world.
Anything I write now goes out as freeware for the same reasons that Toke
gave - it starts off as something I can use and I embellish as I see other
needs (also others needs). I've considered going with a donation option,
but I'm not sure that it would be worth the hassle. Small demand - small
user base - few donations (if any?). So for the time being, if I have time
and the inclination I work on my 'toy'; if I don't then I don't have to
worry about paying customers clammoring for more and more that I may (not?)
feel like doing.
//al