> 5. An amazing number of application developers seem to have forgotten (or
> perhaps never learned) that the "Year 2000 problem" was actually a
> combination of three completely separate but related problems: a) hardware
> clock time representation limitations, b) data structure limitations, & c)
> date manipulation algorithm assumptions.
> 6. A depressingly large number of allegedly competent Macintosh application
> developers are not familiar with the current MacOS APIs, technotes,
> guidelines, and recommendations. (This is no surprise considering the dismal
> quality of most "computer science" curricula, and the complete absence of
> any proper engineering in such curricula).
These last two items are to respond to a number of rather silly emails that
I have received on this subject - I too am getting a bit tired of the way
this discussion is going. The MBU has already posted what they did and I can
see why. They had some good reasons for it, and I accept them. It would be
nice if they could be resolved in a future SR or with the Carbon version,
but it is not critical (I'll just require the unlucky stiffs stuck with the
NT machines to verify the date on the machine manually before they can do
anything else - a shortcut in the startup should do the trick).
--
Eric Hildum
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
To search the archives:
<http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
