Chuck Guzis wrote:
On 12/13/2005 at 11:15 PM Jules Richardson wrote:
Except we're talking about software here
which doesn't deteriorate or get
damaged by someone else using it. If the same were true of cars, I'd have
*no* problem in someone else making use of my vehicle if it wasn't
inconveniencing me in any way. It wouldn't make any difference to me
whether
they used it
or not.
And what if it's software (or a book or a song) that you wrote yourself?
After all, a book doesn't deteriorate by someone else using it or by being
copied and, thanks to modern technology, I can digitize said book and
distribute it over the web, thereby saving some poor trees and cutting down
on greenhouse gases. Wonder what would happen if I posted the latest Harry
Potter book on the web as a public service? I'm sure Ms. Rowling wouldn't
mind, so I don't need to ask her, right?
Ahhh, I was merely pointing out that the car analogy didn't stack up, nothing
more :) I agree with you totally, and personally I'd ask permission first in
the software case.
Problem is in a lot of cases software comes from big companies, and big
company mentality gets in the way. Assuming the company even bothers to reply
- which doesn't always happen - the answer's invariably no. I think this often
stems out of a belief that if the software no longer benefits the company then
it shouldn't be put in a position where it could possibly benefit anyone else.
That and someone invariably gets in a tizz about support issues (although
pointing out up front that you expect no support whatsoever seems to help,
although they generally still don't entirely believe you)
IME, smaller companies and individuals* tend to be much more flexible, thankfully.
*that's regular-sized individuals, not smaller ones ;)
cheers
Jules