Live data from Hacker News

Windows UI evolution: Clicking an unassociated file

movq.de

101–110 of 121 posts

Re: Windows UI evolution: Clicking an unassociated file

#101
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…

It's crazy that people keep talking how fast the computers were. They weren't. It's amazing that they could work with so little hardware resource compared to what we have now, but old PCs were not "snappy" in any way.

Re: Windows UI evolution: Clicking an unassociated file

#102
post #55

Earlier quoted context omitted.

I'd replace 9x by windows 2000. It was the only decent windows. 9x were BSOD crashfest, 2000 was stable as NT but without the enshittification of XP (ugly default themes, stuff above calling internet services with zero value). I think what you describe as responsive are 2 things: 1. absence of animations. I don't know about windows but on linux DE you can disable them, it feels snappier but more raw and I think most…

It's interesting how many people don't like the XP theme. I think it was cool, it was productive yet colorful, but I have to wonder if that's just because it arrived when I was at a certain life stage, the same way I had no problem with the COVID lockdown. We used XP in high school computer class the whole time I was there.

In the good Microsoft tradition, you had programs where this theme will not be applied, just like in Win 10 and 11, leading to inconsistencies.

Re: Windows UI evolution: Clicking an unassociated file

#103
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.…

> XP was the first to bring NT architecture to desktop

That was Win2k (DirectX). XP was full of bugs and holes before SP2.

Re: Windows UI evolution: Clicking an unassociated file

#104
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…

> Today's interfaces are much cleaner

They can do better. Eliminate any distinction between elements and between background and foreground. Cleanliness at its best. Computer are toys anyway, nobody "works" on them anymore. /s

Re: Windows UI evolution: Clicking an unassociated file

#105
post #56
post #18

Earlier quoted context omitted.

> 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 think this is a consequence of cultural changes in the last decades. It used to be normal to be able to open a settings window, or any other window, and read it, top to bottom or in any other order, and then you'd know what was there and where it was and which parts you don't care about. I think it's much better than hidden features practically. But now we've developed this cultural aversion to complex-looking thin…

> cultural changes

Or the lack of it, FWIW

Re: Windows UI evolution: Clicking an unassociated file

#106

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.

I don't remember it ever finding anything. Similar to the find driver dialog (until Win10 or so).

Re: Windows UI evolution: Clicking an unassociated file

#107
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…

[dead]

Re: Windows UI evolution: Clicking an unassociated file

#108
post #18

Earlier quoted context omitted.

> 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 wi…

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

Have you ever played "spot the bird in the forest"? Let's not turn our interfaces into that. OTOH, I do grant that there are personal preferences in play as well. There is, for example, the phenomenon of Japanese web design previously discussed here on HN: https://news.ycombinator.com/item?id=47122789

> New UIs often don't have relevant information

That information is usually implicit. You're supposed to know that a scrollbar will materialize once you've moved the pointer to just left of the right edge of the bounding box. We've interacted with these elements enough to be able to not be confused just because that particular element is not always in my face. Same for 3D buttons, a well-designed interface doesn't need such heavy cueing. A "Send" button shouldn't need any more than the semantics of the word already implies to make it clear it's clickable. Unless one wants to start clicking buttons before reading (and understanding!) the text. It's the UX inconsistencies, design flaws and general bugginess I've already highlighted in my comment that are making this more painful than it needs to be. Though it's not scrollbars that frustrate me on latest macOS, that part works comparatively well as far as I'm concerned.

Re: Windows UI evolution: Clicking an unassociated file

#109
post #75

Fun fact: on modern Windows, if you uninstall modern notepad using the Settings app to get the old one, you won't be able to associate .txt files with notepad.exe without a registry trick: https://superuser.com/questions/1750222/how-to-open-file-typ...

Modern Windows has big problems with file associasions: default to web browser, sometimes asks, sometimes it chooses a random program (for images). Old Windows (9x, 2k, XP, 7) was better.

Re: Windows UI evolution: Clicking an unassociated file

#110
post #54

Earlier quoted context omitted.

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.

That is true, but the discussion here is about speed, not reliability.

Would you rather have a clock which is stopped or always running fast?
Post reply on HN