Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
55% Positive
Analyzed from 1535 words in the discussion.
Trending Topics
#windows#more#file#gnome#evolution#don#used#kde#while#eyes
Discussion Sentiment
Analyzed from 1535 words in the discussion.
Trending Topics
Discussion (27 Comments)Read Original on HackerNews
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, he managed to capture what I was trying to say in more details, with nice screenshots: https://movq.de/blog/postings/2026-06-16/0/POSTING-en.html
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 find across a whole document or getting a word count took time.
Remember windows used to have an hourglass cursor? You used to have to watch that thing flip and empty multiple times when doing things like emptying the recycle bin.
Windows 9x was typically not running on a permanently networked computer. The computer wasn’t running a bunch of background network tasks like checking for updates or polling your email - generally it was just being slow because it could barely cope with running more than one program at once.
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 than go back.
One problem I see is that while the UI itself has been simplified, incidental complexity has crept in other ways. Most importantly, the OSes themselves as software systems have clearly grown ponderous and unwieldy so that today they are more bugs and more of those bugs can be subtle and surprising. Also, there is less uniformity in UX across apps (and UI frameworks).
If you take today's interfaces to an extreme, you would get a white sheet. Very clean, but unusable. I wouldn't call interfaces "clean" where users increasingly have trouble figuring out what's clickable, how to scroll, move or resize a window.
Sure hope they keep producing them because finding a different model that works for me would be kind of shit
I don't know that either, but I remember there were websites specifically for that purpose, where you could look up a file extension and what program to open it with.
> Now there's a big gap. I don't have access to anything between Windows XP and Windows 10. So, Windows 10 (2015) is next
I'm guess these are just what the author already had set up. They're not really difficult to find or set up in a VM...
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.
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
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 never told me that; it just silently failed to download anything, I could not choose any local file for file upload. I only found out eventually, but when I found out, the fix was easy, but still, the question is why such things break silently. This is simply incredibly poor engineering and design, and that happens on linux too. That way they'll never achieve linux desktop of the year. The decision makers here are just horribly bad at designing anything. The whole GTK team fell victim to this, now that it is a GNOMEy toolkit only.
When we ever get one-toolkit-that-fixes-everything (well ...), hopefully they are really allowing only mega-smart people who can think objectively and try to IMPROVE things rather than regress or take away functionality willy-nilly style (as the GNOMEy devs do).
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 lag spikes.
One day, when I die, and go to heaven or hell, when I arrive, my first question to the ones receiving me, will be "Finally, tell me - is there ANY possible way to navigate upwards to the parent folder, in GNOME?"
You click the previous folder in the navigation bar.
Valve adopted them afterwards and now everyone in the KDE team wants to join the ride.
The latter kind of evolution events, while very rare, had a greater importance by being the origin of various kinds of very successful living beings.
Your example shows that because evolution proceeds through random search through the space of solutions, inside the neighborhoods of the starting point, followed by the choice of the best solution among the candidates, it frequently fails to find a global optimum, but it remains stuck on a local optimum.
However, octopuses were not before mammals. Both octopuses and mammals had appeared around the middle of the Mesozoic, but this is not really relevant for their eyes, which already existed in much older ancestors, hundreds of millions of years earlier.
Cephalopods and vertebrates with complex eyes already existed during the Ordovician. Chordates with complex eyes might have already existed quite early during the Cambrian, most likely before the separation between cephalopods and other mollusks, at a time when mollusks must have had only simple eyes that could detect light and perhaps the shape of shadows, but which could not form images.
When cephalopods separated from the other mollusks, they did this by evolving the ability to swim, instead of being forced to crawl on the bottom like most mollusks. (Swimming was achieved by filling their shell with a gas, which made it buoyant, while the other mollusks were held on the bottom by the weight of the shell.)
Chordates have also separated from their ancestors by evolving the ability to be fast swimmers (the elastic and incompressible dorsal chord reduced the energetic cost of anguilliform swimming in comparison with that for worm-like bodies that need to contract a muscular layer in order to prevent the shortening of the body when it is flexed).
This is likely to not be a coincidence, so the evolution of complex eyes in chordates and cephalopods is likely to be linked with the evolution of swimming in both groups, which made important the detection of objects located in various directions, while for a bottom crawler it could have been sufficient to sense when a shadow appeared due to something coming above it.