4 ms·

Oh come on, the seconds are entirely predictable, run from 00 to 59, so basically storing 10 frames ("0" to "9") in the font and foreground/background colors, t

Oh come on, the seconds are entirely predictable, run from 00 to 59, so basically storing 10 frames ("0" to "9") in the font and foreground/background colors, the location on the screen into a small reserved buffer in whatever piece of code is responsible for the final screen frame handover, and this could be updated with minimal overhead and without a context switch,... Yes, it would require a small API addition to the desktop server (wayland, X11, ...) to "register"/transfer/update those 10 frames, their locations ... whenever the user initializes or changes the fonts, font size, ... the context switch can be totally eliminated.

fkrkrkgkgk 1y ago
It’s a feature to exercise the whole display stack at every update, to make sure it works, for example when running remote desktop (or any other similar protocol/stack like citrix), where you can observe if the network still can send packets every second. Otherwise you need to wait a minute before noticing connectivity issues. Both rdp and citrix are extremely fragile and a clock that updates every second is a very good visual indicator for monitoring the connection. https://xkcd.com/1172 https://xkcd.com/1172