Williams, Jim wrote:
When I see all the bugs people find with no apparent difficulty, I am also led
to wonder what other bugs are lurking in the program, waiting to be unleashed
by some poor unsuspecting user.
I would suggest that to talk of the "bugs people find with no apparent
difficulty" is gross mis-identification of the phenomenon. If we were
all running Finale on identical hardware, with the identical software
environments, that might be a different matter, but this is not how
things are in the real world. If any two of us are operating in exactly
the same environment, including hardware and software, it is by because
they set out to do this by design, not by accident; it is much more
likely that every installation is unique, and I'm suspect that some of
these bugs, such as the "Scary bug!" of the subject line show up, only
in particular hardware and software environments, and I frankly doubt
that people are actually looking for these items, rather like the
innocent pedestrian crossing the street in a crosswalk with the light,
who gets injured when a driver strikes the car waiting for the light,
and causes that car to strike the pedestrian, these people are victims
of unfortunate circumstance.
And I would also suggest that, like the pedestrian, who can minimze his
chances of being injured by being conscious of his surroundings, and
actively making his safety a priority, that there are steps that
software users can take, too, to miminize the chances of being "injured"
by the odd software conflict. For my part, I not only actively back up
to two separate systems, I also minimize the number of projects and
processes active at any one time; if I'm not using something, I turn it
off; I don't print in the background, and edit in the foreground. On
anything crucial, I wait for playback to finish before trying to do
something else.
ns
_______________________________________________
Finale mailing list
[email protected]
http://lists.shsu.edu/mailman/listinfo/finale
