Many years ago when I was an undergraduate, I was told that the woman in charge of computer services for us cared mostly about whether her catclock worked. I don't know how true that was, a best part of a decade later I worked for them and would have easily been able to ask, but she'd moved on.
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.
These items I will miss once wayland replaces X. There are hundreds of these utilities and will eventually cease to compile on modern Linux Systems. This one is one of the better ones.
Xorg minus Xwayland will probably go away in the next five years. It's unmaintained, deprecated software. Xwayland will be feature frozen, deprecated except for legacy apps, and eventually it too will wither away.
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.
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.
Maybe, I doubt it though. If it's open source seems like someone is likely to spend the hour or two to migrate a cute little X11 widget (like the Xclock) to Weyland.
FreeBSD probably will at some point. Some FreeBSD developers are even considering adding systemd -- or an equivalent -- to their OS (and no, not launchd, which has a few drawbacks and too many Apple-isms to be a general BSD init).
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.
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.