2 ms·
But the data itself is not new software. It is just data. Functionality should not change because of new data. Well, ideally, yes. But software breaks all t
by sbierwagen 11y ago
But the data itself is not new software. It is just data.
Functionality should not change because of new data.
Well, ideally, yes. But software breaks all the time when you give it data the programmer didn't expect, which happens especially often with time.
DST, for example. What if a state stops observing DST? Arizona observed DST in 1967, but hasn't since then. A couple other states are considering abolishing it, too. You can easily imagine software doing something dumb when it can't find its DST entry in tzdata.
- laut 11y agoI don't think it is a good idea to shield bad software at the expensive of having incorrect out-of-date data. Developers should be aware that tzdata changes all the time, and create software that can deal with it.