For the fun history, @DonHopkins had a thread a few years back:
Now it's all about how to make it useful to the company.
<YOUR FILES ARE NOT BACKED UP, WOULD YOU LIKE TO TURN ON ONEDRIVE?>
<Yes> <Maybe later>
Anyway, the links in that post have deteriorated.
Here's the link to Raymond Chen's blog: https://web.archive.org/web/20190218080905/https://blogs.msd... (shame on MS for redirecting you to another page when showing you a 404, which make it harder to find the original URL).
Updated link to Raymond Chen's blog, where the comments have been 'retired': https://devblogs.microsoft.com/oldnewthing/20080619-00/?p=21...
And the 2 imgur links (same issue with the redirecting...):
https://web.archive.org/web/20230509182201/https://i.imgur.c...
and
https://web.archive.org/web/20230507201645/https://i.imgur.c...
If Microsoft spent money on UX research that improved its UI controls, it would benefit a lot of people. Essentially the cost of that research was bore by all application developers.
The problem now? Every company is designing their own UI components. Every company has to bear the cost of UX research individually. It’s a lot of wheel re-inventing. UX easily takes a backseat.
I wish we could pay them to do something useful instead.
_Re_designing. And _updating_ ... /s
(Only ignorant fools would start to fight it.)
and give them a modern touch or rewrite them to some modern language D/Zig but exactly.
I think this is what as a community should be also doing. It should be also a curriculum in universities.
Thanks to Internet Archive.
[1] https://cdn.dribbble.com/userupload/41647820/file/original-8...
Instead we get these spinning wheels that are like "maybe in the future this wheel will stop and we will have a return value." No confidence whatsoever.
I know this is true because Apple tries to implement progress bars in IOS like real chads. But their progress bars are just fake. They are a cheap animation all the way up to 90% and just stop moving until the progress is actually complete which could be 5 seconds of 90% and 40 seconds of the last 10%. So they think they are chad but lie.
Back in The Day, Mac OS X Tiger just faked it by measuring how long it took to boot to LoginWindow, writing that number of seconds to a file, and displaying the next boot's progress indicator as a percentage of that time.
Power words: `/usr/libexec/WaitingForLoginWindow` and `/var/db/loginwindow.boottime`
- https://daringfireball.net/misc/2005/04/tiger_details#waitin...
- https://web.archive.org/web/20060427030025/http://www.macosx...
- https://arstechnica.com/gadgets/2005/05/397/
- https://web.archive.org/web/20060506092123/http://www.macosx...
- Observable fact: Taking the computer from a fully-powered-off state to a usable state happens when the user presses the power button, involves loading the operating system from slower disk to faster memory, and takes some amount of time to complete.
- Observable fact: `WaitForLoginWindow` is the first “Aqua” UI element one sees after powering their computer on, the first visible thing that's drawn by the operating system that's being loaded instead of drawn by OpenFirmware or by BootX.
- Observable fact: Aqua has an `NSTabView` control used for grouping panes of related UI elements. In original 2001 Aqua, NSTabView looked like something that “stuck out” toward the user from a window. In Panther (2003) it was redesigned into something that looks “sunken in” to visually allow for nesting multiple layers of grouping.
- Observable fact: Panther-style NSTabViews get progressively darker as they are nested, indicating controls which are “more related”. See here for an example of four layers of nested NSTabView: https://cdn.arstechnica.net/wp-content/uploads/archive/mac-o...
- Observable fact: Any OS X user will be familiar with `NSProgressIndicator` as the UI control they see when they tell their computer to do something and some aspect of the computer itself (like disk or network bandwidth) is the limiting factor causing their action to be non-instantaneous.
- Observable fact: The progress indicator is the only part of `WaitForLoginWindow` that moves, and it's grouped with a text label reading “Starting Mac OS X…” in what looks to be a `noTabsBezelBorder`-styled `NSTabView` even though the grouping-box and even the “Starting” text are actually just a static image that the Wait window draws and overlays the progress indicator on, not really Aqua controls because the UI frameworks are still being loaded.
- Illusion magic: Look at the Tiger boot screen, compare it to the previous link, and notice how the fake grouping pane is as dark as what four nested levels of real NSTabViews would be: https://cdn.arstechnica.net/wp-content/uploads/archive/journ...
The coloration makes your own brain tell you that the progress indicator and the “Starting Mac OS X” text are as related as any two UI elements could possibly be, more related than any other pair of UI elements you will ever encounter in Mac OS X, because no reasonable application designer would ever nest four layers of NSTabView.
Since the progress indicator is so strongly visually grouped with the “Starting Mac OS X” text, and every Macintosh going back to 1984 has displayed some form of “Welcome to Macintosh” text while the OS is loading from disk, and progress indicators are the UI element for long-duration user-initiated work, and the computer was fully off so pushing the power button was the only thing the user did, and the wording of “Starting” means it isn't fully “Started”, then the progress indicator must represent how much of the OS is loaded in the current session, right?
That said, back in DOS era, this kind of thing was much more straightforward because most operations that would warrant a progress bar involved some kind of disk I/O, which - if you amortize it - is fairly linear, so one can estimate the completion time relatively well. In more complicated cases - e.g. Win95 installer doing things like hardware detection - those estimates were often wildly off.
I'm sure I could have made the progress bar move more smoothly, but it would have required restructuring my entire program. (It probably needed it, but for a simple script I ran occasionally, not worth it.)
Hard drives and networks are both so fast that you rarely are waiting for data to stream, you're just waiting for the stream to begin
[1]: https://cdn.dribbble.com/userupload/20351752/file/original-b...
It would cycle through a small number of text values with some kind of backspace/overwrite to keep things localized to where the cursor ought to be.
One version was a variable length ellipses: . .. ... that would grow and reset in place.
Another was an expanding "dot": . o O that would cycle in place as one character.
And the early "spinner" was: - \ | / that would cycle in place as one character. Hmm, not sure this will render properly on HN but it is hyphen, backslash, pipe, forward slash.
(c.f: https://ftp.netbsd.org/pub/NetBSD/NetBSD-release-10/src/sys/...)
https://bjk5.com/post/44698559168/breaking-down-amazons-mega...
Reminds me of the first time I ever used classic Macintosh System OS, and how you have to hold the mouse button down to keep menus open. It doesn't take much to throw everything off.
https://bjk5.com/post/44698559168/breaking-down-amazons-mega...
It seems functional to me!
Kudos to the author!
(takes less memory than Miro, at least in Firefox :D)
No half fakes allowed.
There was a cambrian explosion of tools to customize the look and feel. TweakXP pro is the one I remember. All pirated off-course.
That was surprisingly short-lived though, such custom experiences are uncommon these days. Seems like nobody is theming Windows- they just fill it with crapware.
We found more fun in ricing our linux desktops :) https://reddit.com/r/unixporn
Taskbar grouping.
ClearType.
Remote Desktop.
More games ran on it (mostly thanks to higher DirectX version).
From developer perspective, XP was the first version of Windows with registration-free COM and side-by-side assemblies, which (if used properly by app devs) fully solved the "DLL hell" problem.
Better support for dealing with "we never tested outside of windows 98" apps.
early version of SxS.
Various small enhancements.
Didn't care for the UI, though - looked childish...
As for UI, it was very easy to switch to classic mode.
No, it didn't. You had to use some 3rd party software for that.
Nice effort though.
I'm sure some here could look at a screenshot of the same text rendered on Windows, macOS, and Linux and tell them apart.
The only thing I miss is the search bar - I became quite used to that with Windows 7.
I never needed search in XP cause I knew where everything was.
Since Windows 8.1’s fucking abomination of a Start Menu, yeah, I’d miss having search.
That will be fun in the office :-)
What would be the reasons this wouldn't run on Firefox? Genuine question from a non-web developer.
Essentially the browser split comes from the usual browser split: discrepancies in JS and CSS implementations
The only issue I had was the mobi reader wouldn't work, but that was fine with me.
I was expecting Python 2.2 or 2.3 ... not sure what was the earliest version of Python on Pyodide
I absolutely love just how much depth there is to the functionality in this (from being able to use apps like word, or being able to drag and move around icons on desktop).
Brilliant!
Throw in POSIX compliance/bash, first party Linux compatibility (not WSL), window snapping, dark mode, maybe a spotlight-like search and a few enhancements to the file manager and you'd have a pretty much perfect desktop/productivity OS.
Why can't we have nice things?
> maybe a spotlight-like search
As I recall, XP had a background indexing process, to facilitate system wide search.I distinctly recall having to turn it off as I had builds fail more than once because the indexer had a derivative file open that the build was trying to delete.
Locking open files has been a Windows pet peeve of mine for decades.
...but I've yet to experience the level of DE stability you get from Windows XP/7
That also applies to Windows 11 (low bar, I know) and MacOS.
It is getting much better and that's happening very quickly - but there is always some jank.
For instance, dragging a Chrome tab off the current window to create a new window. The various file managers in Linux (dolphin, files, thunar) fall short (also MacOS Finder is an actual joke).
Also matching glibc versions when distributing software is a bit tedious
Have you used Cinnamon? I used Cinnamon for five years and the only weird quirk is needing to change the keybind for locking the machine (Power key + L defaults to opening some stupid debugger).
Used to spend lot of time when I was a kid (I didn't even see a real pinball machine before)
Judging by the amount of Windows startup sound compilation videos out there, "the kids yearn for desktop UIs" might just be a little more common than you think.
And this game is very old. I remember trying to get native-looking dropdown menus in IE6.
Very well done...
The BIOS splash text loads and animates but not much else. I'm using Palemoon 25 (SSE1). Impressive that it loads at all!
It's just a shame about the antitrust stuff and the bugs and glitches that came with MS Windows
https://blogs.windows.com/msedgedev/2025/01/27/stand-up-to-s...
People rarely complained that finding an application under the Start menu was difficult. In current versions of Windows, the Start menu is such a disaster, such a mess, that people don't even open it and rely much more on the search function.
If running in some isolated VM for some superspecial APP still supporting running on 2000, why not? Uses much less memory.
It's very funny to look at Apple progressing from "looks like Vista" to "looks like Win7" in its iOS 26 betas.
[edit]: I forgot to mention as well, at least on arch you dont have to install the (I forget the package name exactly) kde applications package off pacman, if you don't install it you'll need to install dolphin and a few other things but it really cuts down the bloat.
But some of my Clients use windows and were just "forced" to upgrade their hardware and use Windows 11.
Edit: Just realized that this is not a VM, just a replicate. No wonder Word 2003 looks weird.