Kit-Kat Xclock
github.com
github.com
There was a method to this apparent madness though, because her catclock wasn't running on her computer, it was running remotely over X. So if the catclock worked, this meant the network was up, and key services to the remote servers worked.
If one of your classmates has remotely unplugged your mouse that's annoying for you (this is mid-1990s so telnet rather than SSH and by default X sessions are open to the world) but she has more important things to focus on - however if the entire network is down that's worth her time.
And when will that be? People have been singing the death of X for years now but there's always something keeping X around.
They may kick around as curiosities and relics of the past, much like Flash did, but X's status as a first-class, supported member of the Linux ecosystem is finished.
EDIT: Oh, look: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests...
A Red Hat is prepping to start making xwayland-only releases of the server, since nobody has any plans for any new actual server releases. This is probably the beginning of the end for non-xwayland DDXen.
The only people who cares about that are the ADHD-riddled developers who will anyways deprecate Wayland in seven years, only to re-implement X11 again, this time in rust.
The rest of the world will keep moving and working with the "unmaintained" software while the kids play with their shiny new toys.
Right after the "stty" command is retired? :)
And again, since X is virtually abandonware at this point, the remainder of the BSDs will follow suit, especially since most of the open source kms drivers are shared between Linux and *BSD. It's really on the compositor maintainers to support the BSD kms back end in their compositor code, though.
Title is wrong!
It should be: «Kit-Cat xclock»[0]
> ... The graphics were inspired by the famous, indeed iconic, Kit-Cat (R) clock, one of which still hangs in my kitchen.