Good arguments for any given program, just hard to imagine they’re still valid for a clock. There’s no other example i can’t think of that a clock has noticeable startup delay or even update time. In the most charitable wording this is exceptional, a unique example amongst the broadest class of programs.
I now realize it’s probably not worth attempting to convince me to not be cynical, i’m having as much trouble as OP with this lol. Thanks for your thoughts though.
Oh, don’t get me wrong. It’s odd for a clock to act this way, just not inexplicable. At best it’s an example of UI standards being applied without regard to sense, which is very much in line with Microsoft.
Most other clocks will do something similar, they just do it in the background. Something that’s a lot easier to do if you’re not following a UI framework that says you’re never allowed to change something in a way that might cause the user to see a weird shift. Other things just acknowledge that clock sync should only take a few milliseconds before the clock is even visible, that a timezone DB update will rarely cause a change of more than an hour, and that a user will probably not even notice if there’s a shift.
Good arguments for any given program, just hard to imagine they’re still valid for a clock. There’s no other example i can’t think of that a clock has noticeable startup delay or even update time. In the most charitable wording this is exceptional, a unique example amongst the broadest class of programs.
I now realize it’s probably not worth attempting to convince me to not be cynical, i’m having as much trouble as OP with this lol. Thanks for your thoughts though.
Oh, don’t get me wrong. It’s odd for a clock to act this way, just not inexplicable. At best it’s an example of UI standards being applied without regard to sense, which is very much in line with Microsoft.
Most other clocks will do something similar, they just do it in the background. Something that’s a lot easier to do if you’re not following a UI framework that says you’re never allowed to change something in a way that might cause the user to see a weird shift. Other things just acknowledge that clock sync should only take a few milliseconds before the clock is even visible, that a timezone DB update will rarely cause a change of more than an hour, and that a user will probably not even notice if there’s a shift.