Time Machine Release Stalled Due To Lack Of Interest...

It's curious to me why Microsoft is not a frontrunner of providing more support for date time globalization and localization. It's an issue that touches most applications in one form or another, yet, nothing is really mentioned about the lack of support from MS. Here's a quote from a MS Staffer, who sheds an interesting insight on the lack of historical support for date time:

Requests for a "historical" DateTime have been very infrequent. We are unlikely to provide such a thing in the Longhorn timeframe due to lack of demand. There may be a good 3rd party opportunity for a library for historical dating that interoperates well with the DateTime class.
- Tuesday, April 20, 2004 11:59 AM by Anthony Moore
http://blogs.msdn.com/brada/archive/2004/04/13/112784.aspx

Now, I don't really know if Mr. Moore is still engaged with Microsoft or just what his exact role is in the DateTime area, and don't mean to be overly critical, but... isn't the fact that this feature is missing something that should fuel effort? I mean I really didn't ask for the .Net initiative, or better performance and security models, but these seem to be good things. Isn't knowing that date time information is correctly displayed something of value?

Now, in all fairness, I've posted several times on the ASP.Net forums regarding date time issues, and asked for folks to share their comments regarding the need for correcting this oversight within the Microsoft world, offering to share my research and proposals - I got 2 responses. So, maybe Mr. Moore is correct, maybe there is no interest in the issue.

I'll forge ahead anyway, just means I'll just need one seat in my time machine afterall, I won't need the extended cab version. Drat, I will have to delay production to retool the assembly though.