XPost: comp.os.linux.advocacy
From: djkaaa@eduv.com
On Fri, 26 Dec 2025 20:17:09 -0500, Joel W. Crump wrote:
> On 12/26/25 8:10 PM, 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.
>
>
> There's no question that Linux handles this the appropriate way, in
> contrast to M$ treating the user as a manipulable paying customer of
> arbitrary, proprietary corporate junk, it wouldn't stop me from using
> Winblows, but I scoff at Microsoft's platform really being the true
> standard. Linux won.
Until next month when you once again switch back to Windows and start
this perpetual troll over again from the Windows side of things.
Rinse and repeat.
You need to become more creative with your trolling Joel because your
usual concern troll gimmick no longer works.
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
