Live data from Hacker News

Windows UI evolution: Clicking an unassociated file

movq.de

31–40 of 121 posts

Re: Windows UI evolution: Clicking an unassociated file

#31
post #18
post #3

I think Windows 9x was peak Windows. Everything is clear, you know what's a button and what's not. Information density is also high, which is a good thing on a computer screen. But the main thing is that Windows 9x felt responsive . The Windows widgets felt solid and performant, while "modern" UWP apps feel clunky and prone to breakage. And don't even get me started on Electron. Edit. See OP's previous article here,…

> Everything is clear, you know what's a button and what's not. Information density is also high, which is a good thing on a computer screen. I would say information density was too high. All those always-on indicators: 3D scrollbars, buttons, etc. create a very busy picture. Today's interfaces are much cleaner which comes at a price of less information and hence, more ambiguity, but I for would rather pay that price…

> I would say information density was too high. All those always-on indicators: 3D scrollbars, buttons, etc. create a very busy picture.

Have you been in nature recently? We've evolved to deal with very busy pictures and parse relevant information from them.

New UIs often don't have relevant information - like what is clickable or scrollable - and that's a problem.

It used to be that grandpa couldn't find a button with his poor eyesight, since everything was cramped and too tiny on the small screens we used to have.

Nowadays the clickable label is hidden behind a tiny hamburger menu that you can't tell apart from a mere stylistic flourish on the massive screens we keep mostly empty. Now neither of us can find the button.

That's progress? Every time I open an old application I breathe a sigh of relief because I can feel the cognitive load decreasing. Not having to put myself in the headspace of the designer to figure out what random geometric shape happens to be interactive is like taking a vacation.

Re: Windows UI evolution: Clicking an unassociated file

#32
post #3

I think Windows 9x was peak Windows. Everything is clear, you know what's a button and what's not. Information density is also high, which is a good thing on a computer screen. But the main thing is that Windows 9x felt responsive . The Windows widgets felt solid and performant, while "modern" UWP apps feel clunky and prone to breakage. And don't even get me started on Electron. Edit. See OP's previous article here,…

Windows 9x did not feel ‘performant’. This is a false memory people seem to have. Spinning rust hard drives were slow. It took ages to launch a program - loading screens typically had time to display a progress bar and a series of notes about what they were up to - ‘loading extensions’, ‘reticulating splines’, etc. Word would stall whenever it was autosaving. Carrying out an operation like spell checking or doing a f…

Word 2.0 forever made me distrust Microsoft with an error: "File too large to save."

It was on a 20Mb hard drive, and the file was small enough to fit on a 1.44Mb floppy.

Turns out it was an obscure defect in Word: if you had quick save on, and the last page had a diagram or image, it would choke. Quick save or fast save - I forget what it was called. This would append deltas to your file, I think.

Re: Windows UI evolution: Clicking an unassociated file

#33
post #28
post #3

I think Windows 9x was peak Windows. Everything is clear, you know what's a button and what's not. Information density is also high, which is a good thing on a computer screen. But the main thing is that Windows 9x felt responsive . The Windows widgets felt solid and performant, while "modern" UWP apps feel clunky and prone to breakage. And don't even get me started on Electron. Edit. See OP's previous article here,…

Nah, that goes to either Windows 2000 or Windows 7.

Windows 2000 Professional was peak Windows for me. Skipped XP etc thanks to mac. Then 7 for a while.

Re: Windows UI evolution: Clicking an unassociated file

#34

Can it really be called evolution? That sort of implies an improvement. Interestingly enough, the default GTK file chooser also sucks. I notice this nowadays because I broke something in my setup but I don't know what, and the default file chooser does not remember anything I do. Prior to that I found out that for opening files via the browser, I need to have e. g. xdg-desktop-portal-gtk running. Well, my browser nev…

One thing that drives me nuts every time I save a new file or 'save as'. File chooser appears and I automatically start typing to enter/change the filename. But the filter input always gets focus and now I'm filtering the list of visible files instead of naming my file...

(Yes, I know I could try to submit a PR but I don't have the energy to figure out the Gnome governance process.)

Re: Windows UI evolution: Clicking an unassociated file

#35
post #3

I think Windows 9x was peak Windows. Everything is clear, you know what's a button and what's not. Information density is also high, which is a good thing on a computer screen. But the main thing is that Windows 9x felt responsive . The Windows widgets felt solid and performant, while "modern" UWP apps feel clunky and prone to breakage. And don't even get me started on Electron. Edit. See OP's previous article here,…

I think Windows 9x was peak Windows.

I'd choose XP instead. People disputing the performance maybe should consider the hardware at that time. Real problem with 9x was low-level stability. Juggling with compatibility was difficult, file access comes to mind, it was a kludge. It was possible but hard to maintain the system in a sensible state.

XP was the first to bring NT architecture to desktop. It was a huge success. Many despised the colorful UI, I actually like it. They started moving things around, but annoyances were fixable. Microsoft has adopted more of a "my way or the highway" attitude since.

Re: Windows UI evolution: Clicking an unassociated file

#36
post #27
post #13

Earlier quoted context omitted.

at this point GNOME is a joke. I'm not sure KDE is always better but at least KDE is clearly trying. btw Wayland is also a project of the GNOME team and almost everyone is using the KDE extensions to it to make it suck less.

I daily drive GNOME on Ubuntu 22 on a daily basis and its UX is the favorite of all the UIs I've ever used, and I've used classic mac, OS X, all windows versions, xfce, kde and a trillion programs. And both android and ios devicess, both from early versions onto recent. And GNOME really shines here. I'm on X11 though. Wayland lagged my mouse when I tried it years back, so I gave up on Wayland. Maybe they've fixed the…

4-year-old unsupported OS. X11 support was removed from GNOME this year.

Re: Windows UI evolution: Clicking an unassociated file

#37
post #3

I think Windows 9x was peak Windows. Everything is clear, you know what's a button and what's not. Information density is also high, which is a good thing on a computer screen. But the main thing is that Windows 9x felt responsive . The Windows widgets felt solid and performant, while "modern" UWP apps feel clunky and prone to breakage. And don't even get me started on Electron. Edit. See OP's previous article here,…

Windows 9x did not feel ‘performant’. This is a false memory people seem to have. Spinning rust hard drives were slow. It took ages to launch a program - loading screens typically had time to display a progress bar and a series of notes about what they were up to - ‘loading extensions’, ‘reticulating splines’, etc. Word would stall whenever it was autosaving. Carrying out an operation like spell checking or doing a f…

I have a running Windows 98 PC with P3 550MHz and SSD connected via IDE adapter. The drive is a bit out of place, but it’s legitimately the fastest booting, most responsive computer in my house. Its only speed issue is that it can really do just one thing. Any heavy task (including large file/network operations, apparently) will render the system almost unresponsive until it’s finished.

Re: Windows UI evolution: Clicking an unassociated file

#38
post #7

I imagine that the database for the online file association service for Windows XP has been lost to time, but for those who remember it: was it any good? It seems like quite a good idea now -- if I remember correctly, Windows as of current seems to suggest a generic Bing search, which brings up all the spam "What extension is XXX?" sites. That could have changed; I haven't really used Windows after 11's debut.

If I recall correctly, it was pretty bad. It used to open Internet Explorer on this page: http://shell.windows.com/fileassoc/0409/xml/redir.asp?EXT={e... where {ext} was the extension. Suggestions were vague and they only made sense with well-known filetypes. There's a screenshot of how it looked here: https://protoweb.org/wp-content/uploads/2025/08/screen.jpg

Today that page would be titled "Microsoft Windows Copilot File Associations"

The more things change, the more they stay the same.

Re: Windows UI evolution: Clicking an unassociated file

#39
post #35
post #3

I think Windows 9x was peak Windows. Everything is clear, you know what's a button and what's not. Information density is also high, which is a good thing on a computer screen. But the main thing is that Windows 9x felt responsive . The Windows widgets felt solid and performant, while "modern" UWP apps feel clunky and prone to breakage. And don't even get me started on Electron. Edit. See OP's previous article here,…

I think Windows 9x was peak Windows. I'd choose XP instead. People disputing the performance maybe should consider the hardware at that time. Real problem with 9x was low-level stability. Juggling with compatibility was difficult, file access comes to mind, it was a kludge. It was possible but hard to maintain the system in a sensible state. XP was the first to bring NT architecture to desktop. It was a huge success.…

Yes, maybe XP was the sweet spot between ease of use and ability to revert back to a "classic" Windows interface.

It also had many multimedia features for burning CDs, editing videos, etc..

Re: Windows UI evolution: Clicking an unassociated file

#40
post #24

Can it really be called evolution? That sort of implies an improvement. Interestingly enough, the default GTK file chooser also sucks. I notice this nowadays because I broke something in my setup but I don't know what, and the default file chooser does not remember anything I do. Prior to that I found out that for opening files via the browser, I need to have e. g. xdg-desktop-portal-gtk running. Well, my browser nev…

I never understood why file open/save dialog is a separate thing. I want to use my file manager to open and save files!

Win32 has good news for you!
Post reply on HN