I will note that while we do expend some effort to make our products as
back-release compatible as possible, we also, decades ago, spent many
man-months replacing undocumented hacks with calls to stable, public,
APIs (at the time, the goal was to make the product fully Security 40
compatible), we pay attention whenever anybody finds a way to break one
of our products, and do our best to remedy the problem in as timely a
manner as possible, and *we use our products ourselves on boxes that are
more current than those on which we develop, and therefore stand a good
chance of finding any compatibility problems ourselves.*
--
JHHL
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
