Re: looking at the survey (pricing)

[EAMorical@aol.com]

Still more and more comments. :)

Roger writes: 
>>   - Cost of becoming proficient with new application software
>> 
>> woah. does this apply to me? This seems like a different use of the
>> word 'cost' than the ones I just answered. I don't pay anything to
>> learn new application software. Except time. In which case it is
>> 'important' because I don't want to spend forever becoming
>> proficient with something, but if it's worthwhile then I'll make it
>> happen. Note that for the most part, I don't need to be 'proficient'
>> with something to use it usefully. Perhaps we could clarify, and add
>> "(time or money)" in there.

Pete writes: 
>     I think in either case, time or money spent in the course of
>gaining proficiency with software, it doesn't matter - time *is* money,
>especially if you are using the app as part of your work. If you're a
>home user (I guess I can add academic user here too), it's more time
>costs. So a system or app which is time-consuming to learn before being
>able to gain some measure of productivity will likely be passed over by
>the 'mainstream' user. Many 'mainstream' users (or at least those I
>would qualify as such) aren't those I would characterize as being too
>curious or driven to learn about the apps or os they use. I tend to
>qualify those that do take the time to learn and investigate the app as
>being advanced, or self-supporting, users.
>    As such, any really obtuse program probably wouldn't find a lot of
>use by 'mainstream' users, unless they really have to.

Being familar with the Fortune 500 environment, I can tell you that the
learning curve can be very costly and readily show up in the bottom line.

Bob