|
PureBytes Links
Trading Reference Links
|
Maybe I am missing your point. The technical problems with backward
compatibility will remain regardless of upgrade policy.
Backward compatibility attempts to preserve the overall software
functionality through numerous updates and upgrades. Whenever a new
feature is added, we try to make sure that there is a way to preserve the
old functionality or at least automatically update that functionality to the
new technology. This is done so that the time and effort invested by our
users is not thrown away through each update. Granted, there are times that
we have not been successful in maintaining this backward compatibility but
we are always trying.
Believe me, it would make my job easier if we could completely ignore past
functionality. In the case of our users, however, I fear that we would only
create more frustration than already exists.
Ken Hunt
Programming Manager
Equis International
-----Original Message-----
From: Norman Wiss Jr. [mailto:cutup2@xxxxxxxx]
Sent: Friday, July 28, 2000 10:12 AM
To: Metastock Group
Subject: Frustrations
To Ken Hunt---I can't find the e-mail but I think you mentioned a while back
that new versions of MS were made compatible with versions back to v3. If
so, this needed compatibility certainly required extra work and increased
the complexity of the new features being added. These complexities are
apparent in the e-mails of frustrations and complaints every time an upgrade
is released. To me, it makes sense to give free upgrades to v6 or v6.5 to
all users of earlier versions. The cost should be minimal compared to the
extra hours of programming necessary to give compatibility and would
simplify the program itself. Just look at the e-mails of problems and
frustrations which users and Equis people have endured. Norm
Wiss
cutup2@xxxxxxxx
|