Our Proposal for a Standard Software Product --
A Time Engine

This document is really only in the design stage, and we cannot now supply much more than a hint of what is to come.

Many people think that the Y2K crisis passed and will never reappear, because the Year 2000 will never reappear. Wrong!

The problem was that only 2 digits were used for the year. Do you know how almost everyone fixed it? They used 2 digits for the year! And made a guess on whether it was a 19xx or a 20xx year.

Anyone that gives this a little thought will see that these fixes and patches will not hold up forever. The question is "how soon will they fail?"

My premise is that serious thought should be given NOW to an easy way to replace those patches with correct code, preferably a standard product suitable for all users. In addition to gaining protection against future failure, a product based upon XDay (Bob Bemer's variant of Julian Day) will homogenize usage, make all date programs run faster, and reduce the gargantuan effort everyone will have to expend again eventually.

Come back later, please. It will be interesting! Meanwhile you may wish to read my plans for XDay, as published on Peter de Jager's site, but made current.

Back to Home Page