3 ms·
The biggest downside would be the date rolling over during a record-keeping period. But this is already a problem and people handle it just fine. I mean, we say
by psd1 3y ago
The biggest downside would be the date rolling over during a record-keeping period. But this is already a problem and people handle it just fine. I mean, we say "tonight" for 02:30 on the following day, so meh.
- rightbyte 3y agoNo no no. We can't make the world adjust to our crappy code. 24:00 is "mid night". 02:30 is not less 'tonight' than 21:30, assuming no DST.
- iggldiggl 3y ago> But this is already a problem and people handle it just fine. I mean, we say "tonight" for 02:30 on the following day, so meh. Because that only affects the comparatively small number of people awake respectively events happening at that time of day. If you move the calendar date change right into the middle of the waking hours of almost everybody else, things get quite a bit more annoying.
- psd1 3y agoI'm willing to make that sacrifice if we can delete python's time zone library.