2 ms·
Right, I'm not disagreeing with any of that except to say it's application is not ubiquitous and thus not universally applied despite the fact that it's part of
by hilbert42 4y ago
Right, I'm not disagreeing with any of that except to say it's application is not ubiquitous and thus not universally applied despite the fact that it's part of a common O/S.
If it were then the DST problem would not have arisen or that it would have been much easier and qicker to solve. (That is, not every one understands the issue to the point where it's no longer the subject of debate - ipso facto, the fact that we're having this debate on HN demonstrates that lack of universality.)
A similar system with a niche application which also possesses truly advanced relativistic timekeeping features is the software for GPS satellites. However it too hasn't been universally applied (needless to say, it'd also likely require extensive modification if it were to be adapted for the use that we're discussing here, that said, no doubt the basic algorithms would be adaptable).
- throwaway09223 4y agoNo, these systems are universally applied. You pretty much can't find software which doesn't use the abstractions I describe above. They're baked into every major framework. The DST problem is due to the database that these interfaces use not being designed for rapid updates.