XPost: comp.os.linux.advocacy   
   From: candycanearter07@candycanearter07.nomail.afraid   
      
   rbowman  wrote at 03:04 this Saturday (GMT):   
   > On Sat, 27 Dec 2025 01:10:03 -0000 (UTC), candycanearter07 wrote:   
   >   
   >> General best practice for datetime is to store everything in UTC, then   
   >> only convert to timezones when displaying to the user. Timezones are   
   >> incredibly messy, so using a global standard makes things way simpler.   
   >> Even in one timezone, something like daylight savings can mess things   
   >> up.   
   >   
   > My favorite was Indiana. The state didn't do DST. The problem was the   
   > sections near Gary would run on Gary time. Those on the Ohio border would   
   > run on Ohio time. Half the people were technically on the wrong time half   
   > the year and then they switched. There was a three page pamphlet in the   
   > visitor center on the interstate that tried to explain it. If you asked   
   > someone the time they would say 'twenty after' and let you pick after   
   > what.   
      
      
   It's always fun hearing about poorly planned timezones.   
   --   
   user  is generated from /dev/urandom   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)