[userbinator]

For a bit of comparison, Windows 2.03's (analog!) clock:

    CLOCK    EXE      8960   9-04-87  11:11a

...will run on Windows 2.0 up to Windows 10 x86.

[anthk]

OClock and "aclock" statically built can be run under older kernels up to today's distros.

Oh, and it will run and render over the network with paleolitic Unixen thanks to X :).

[frozenport]

Yeah but doing a static build is probably hard because you need a static build against x?

[anthk]

X works seamlessly, it's a client/server arch. Even if you run emulators, by exporting $DISPLAY to your host (and by running xhost +$EMULATOR_IP) you can run, for example, tools for older Unixen.

Except for SGI, but I am not that sure.

[monocasa]

X's IPC is very stable (which is half the point of X); the instance on shared libraries has more to do with it being a memory hog on the kinds of systems that existed the first couple decades of it's life.

[anthk]

This. If you rum SIMH to emulate a Vax (and some other Unix), most Unix programs requiring X can be perfectly forwarded to use the host's X server. Or some Xephyr server.

[projektfu]

I used to bring up openvms running Motif on a vax through xfree86.