XPost: comp.os.linux.advocacy   
   From: crude@sausa.ge   
      
   On 2025-12-26 8:10 p.m., candycanearter07 wrote:   
   > CrudeSausage  wrote at 23:32 this Wednesday (GMT):   
   >> On 2025-12-24 2:04 p.m., Lawrence D’Oliveiro wrote:   
   >>> On Wed, 24 Dec 2025 14:20:03 -0000 (UTC), candycanearter07 wrote:   
   >>>   
   >>>> Actually, I believe Linux will /always/ set the internal clock to   
   >>>> the UTC time, regardless of how the timezone is set. Windows, on the   
   >>>> other hand, assumes its the local time and offsets accordingly. Of   
   >>>> course, loading into Linux from Windows doesn't screw up the time...   
   >>>   
   >>> Sounds like it is Windows getting screwed up.   
   >>>   
   >>> System time in UTC is the only convention that makes sense. Convert   
   >>> time to some suitable local time zone before displaying it to the   
   >>> user, by all means. But don’t assume that all the users on a   
   >>> particular system are in the same time zone.   
   >>   
   >> Why wouldn't all the users of a system located in one time zone also be   
   >> in that same time zone?   
   >   
   >   
   > 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.   
      
   I imagine that this would be necessary if you had one powerful system   
   that users from many time zones log in to, but I don't see why this   
   would be beneficial or even necessary in 2025. This is one Linux or UNIX   
   advantage not one person of this era would actually care about.   
      
   --   
   CrudeSausage   
   John 14:6   
   I hate Reddit.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)