Oh wow. I re-checked and there’s no way to make the Clock app to show the seconds, so it’s as useless as I imagined. But yes, there is apparently a setting in time and date settings to show the seconds on the clock in the task bar. …And the setting is buried under a fold. With the caveat that it will increase power usage. How does displaying seconds increas power usage fssgsgfffsshhhgg
This question is often asked, but I ask it again: why is Windows?
If you only display hours and minutes, you only need to redraw the clock every minute. If you display the seconds, you have to redraw every second.
And redrawing is not just changing some pixels. The Os scheduler has to wake up the process, put another to sleep. And all of that costs power.
Yes, the clock in the taskbar probably uses less power in an hour than watching a YouTube video will consume in a second.
But it is still a 60x increase in power usage.
This warning is actually a good thing. It means whoever implemented the seconds in the taskbar clock actually has the right mindset for developing an operating system. You don’t use a JavaScript framework to develop the start menu because “all the juniors come from JavaScript boot camps so it’s cheap to hire” you want someone that knows that the OS’ job is to provide a strong base layer that uses little resources so great things can be built on top of it.
Of all the things you could complain about windows, you chose to do it about the actually good ones, when you could go instead for the “30% vibe coded” codebase with a JavaScript UI that can’t even implement a “power off” button.
Oh wow. I re-checked and there’s no way to make the Clock app to show the seconds, so it’s as useless as I imagined. But yes, there is apparently a setting in time and date settings to show the seconds on the clock in the task bar. …And the setting is buried under a fold. With the caveat that it will increase power usage. How does displaying seconds increas power usage fssgsgfffsshhhgg
This question is often asked, but I ask it again: why is Windows?
Well. Doing everything costs energy.
If you only display hours and minutes, you only need to redraw the clock every minute. If you display the seconds, you have to redraw every second.
And redrawing is not just changing some pixels. The Os scheduler has to wake up the process, put another to sleep. And all of that costs power.
Yes, the clock in the taskbar probably uses less power in an hour than watching a YouTube video will consume in a second.
But it is still a 60x increase in power usage.
This warning is actually a good thing. It means whoever implemented the seconds in the taskbar clock actually has the right mindset for developing an operating system. You don’t use a JavaScript framework to develop the start menu because “all the juniors come from JavaScript boot camps so it’s cheap to hire” you want someone that knows that the OS’ job is to provide a strong base layer that uses little resources so great things can be built on top of it.
Of all the things you could complain about windows, you chose to do it about the actually good ones, when you could go instead for the “30% vibe coded” codebase with a JavaScript UI that can’t even implement a “power off” button.