Remember how the original Mac used to plop down icons of all your system extensions one-by-one along the bottom of the screen, in the order that it loaded them, which helped you know how long it would take to boot, and figure out which one crashed your system?

And how all the k001 k1dz had lots and lots of extensions?

Well there was actually a special extension that made you even k001er: you could paste as many and whatever icons you desired into its resource fork, and it would plop them down one by one during the boot, delaying a bit between each.

Sure it took a little longer to boot, but it made you such a bad-ass!

> Remember how the original Mac used to plop down icons of all your system extensions one-by-one along the bottom of the screen, in the order that it loaded them, which helped you know how long it would take to boot, and figure out which one crashed your system?

Iirc Haiku does that in its splash screen. KDE sort of did at some point in KDE 4.x.

> KDE sort of did at some point in KDE 4.x.

I would swear it was KDE 3.x in its splash screen.

https://cdn.pling.com/img//hive/content-pre1/14801-1.png

The icons at the bottom would start in grey scale and be colored as KDE was loading.

KDE 4 also used this style of splash screen (with the icons fading into view): https://news.opensuse.org/wp-content/uploads/2008/02/kde4-sp...

Yeah, now I remember, I removed KDE 4 and its clocks [1] from my memory (it actually made me switch to Gnome and never went back)

[1] basically the initial 4.0 release (which was a rewrite from scratch for the UI/Desktop component) was not usable at all as a daily driver, lots of crashes and missing features. The only thing that worked well from the start were the clock widgets, and they were showcased a lot in screenshot. I think it even reached some kind of meme status by KDE 4.1. But I cannot find any blog post / rant from the time, my search-fu is not that good.

What a clever solution! I like it because it still f gives an realistic indication of how long it will take!

Yeah, that's clever indeed.

Jenkins also does that (estimate progress based on last duration), but also shows estimated status equal to the previous one. If you know what it means, you know what state you're trying to fix or maintain, but it is quite confusing at first.

iOS does this when loading/switching apps. It takes a snapshot of the app as it was when closed, and then when you are loading that app as it was when you closed it it just shows the screenshot until the app state is reloaded.

The hope is that the app is fully loaded before you actually attempt to interact with what you see on the screen.

I think Windows does the same between desktop-compositor crashes and restarts. (When it doesn't get to bad, as than you just get a back screen with the mouse cursor until the compositor isn't restarted).

At least that was my perception as I used Win 10.