I can't help thinking about how much we have lost. Just finding the scrollbar nowadays can be a challenge. Not to mention if you want to resize a pane - in some applications they seem to have taken extra steps to make it difficult to find the line to grab.
Operating systems of that era were designed based on UX research to help people use the unfamiliar operating system.
Subsequent ones were designed by UI designers, and opinionated senior managers, who already knew how to use them, and took out usability features to make them "look nicer". This sort of worked when the opinionated manager was Steve Jobs. Most managers are not Steve Jobs.
> in some applications they seem to have taken extra steps to make it difficult to find the line to grab
Pet peeve of mine in Windows where the line is at most one pixel now. They also took away the coloured distinction between title bars for the active window, so you don't know where keystrokes are going to go.
> Operating systems of that era were designed based on UX research
Too many developers nowadays don't know this. On any HN discussion of UIs, I've been noticing a growing number of younger devs insisting that usability is entirely subjective (their words, not mine). It's not just that they don't know about cleverly thought-out things such as safe triangles in nested menus or all the affordances/signifiers espoused by Don Norman et al. The bigger problem is that they don't know what they don't know, and they come across as being unwilling to learn.
It does make UX discussions frustrating and meaningless when they could, and should, be interesting and a learning experience for us all.
I was trying to use Orca Slicer (which itself is intractable) and it had a combo button whose menu was disconnected from the button. The menu would disappear as soon as the cursor left the button boundary, but because it was disconnected, there was no way to get to the menu without leaving the button boundary, traveling a void, and then getting to the menu. I’m unsure what incantation allowed me to finally choose the right command, but forget how it looks, it was if no one even tried to see if it works.
There are still UX research. It's just that the collective "we" has changed and we can/may build on some existing design decisions.
You are always designing something with a target audience in mind, and the next, e.g. mobile phone will very likely be used by someone who has interacted briefly with a similar device, so you may re-use some already learnt patterns.
The very early UXs built heavily on desktop metaphors (like folders), but at this point many (and an increasing number of) people are more familiar with OS UI n-1 than a typical office setting.
So I don't think jumping to this conclusion is correct - there are well-designed software, it has just become much much cheaper to create new ones, so the average quality has necessarily went down.
> Operating systems of that era were designed based on UX research to help people use the unfamiliar operating system.
I have a lot of thoughts on things like PC usability today. You're right that UX research would have heavily contributed to the design on these older systems. As computers moved from the warehouse to the living room they had to be easier to use and understand for people without CS degrees. I think it is fair to assume *some* things about what people these days are familiar with when it comes to the desktop GUI, but usability should receive more focus now even if it slightly hinders aesthetic. A friend of mine has been teaching a college program for video editing and she has students who needed her to explain what files and folders are. This is not the first time I've heard of things like this.
Smartphones and tablets have obfuscated so many basic functions and features that it is actively harming people's understanding of how to use a computer. Things like window sizing, executables, how apps know where things are, and how programs are installed. Android does allow users to peek behind the curtain more than iOS but Google has been going down the path of locking down Android. I haven't been in an elementary school classroom for like 17 years but I remember having computer lab time where we would learn how to use Windows 95/98. I think what has benefited my friends and others my age (~30) is that we grew up when computers were in the home and were usable enough for us to log in and intuit our way around but there was enough friction that made it so we would have to figure things out on our own.
"Subsequent ones were designed by UI designers, and opinionated senior managers, who already knew how to use them, and took out usability features to make them "look nicer"."
With desktop OS I feel a lot of designers don't know how to use them. They grew up with phones and never use a desktop OS outside of work.
For the brief time I used Windows 11 the amount of times I placed a window over another and then clicked on the wrong window because I couldn't tell at first glance where one started and the other ended was absolutely ridiculous.
I'm afraid that the core of the problem is something far more simple and fundamental.
The people designing desktop apps today simply never learned the conventions that make desktop applications good. They grew up with smartphone apps, web apps, electron apps, games, etc.
In fact, you can observe from things like JavaFX, Flutter, WPF, etc., that the trend has long been about the ability of easily creating custom widgets like you could with Javascript (or Flash), rather than the convenience of having a library of widgets that look and feel exactly the same as every other widget in the system.
"I couldn't tell at first glance where one started and the other ended "
Sometimes I am starting to feel like how my dad looked many years ago when I tried to teach him how to use Windows. He simply couldn't see the window borders. With the latest designs I am reaching this point too. I am struggling moving and resizing windows because I can't tell where the border is.
> look and feel exactly the same as every other widget in the system
Which is what? Windows natively has like 4 official looks. You can click around the 2 (!) settings programs and pop open windows for basically every framework windows has created (and deprecated) in the last 2 decades.
The UX designers copied the look, minus the colors, and without functionality. Whoever thinks, that an 1px border for a resizable element on a 4k display is ok, is insane.
My pet peeve is spacing. My usual resolution is 1920x1080 (scaled or not) and it feels I could cram more information in an old 1024x768 desktop. You have to maximize most windows to get it to show enough information.
>> You have to maximize most windows to get it to show enough information.
At work I use 1 or 2 monitors plus the laptop screen (on Windows). At home I just use a single 55" 4K TV for my monitor and place apps center, left, right, and up top for rarely used stuff (on Linux). The desktop metaphor always wanted a big display but you're right - most Windows apps expect a full 1920x1080 for themselves.
This drives me crazy. Even looking at these old screenshots you just know that these systems we outputting a display resolution lower than 1024x768.
When I was checking out the MacBook Neo a while back I was disappointed that the resolution is not natively x2 scaled. It uses fractional scaling when macOS handles fractional scaling quite poorly. I've set the resolution on my M1 MBP to 1280x800 so it was x2 scaled and clarity improved significantly. But I also sacrificed usable space because apps don't adjust, everything is just made larger.
Double-click came out of Xerox's research park. Apply might have been the first to put that into a popular desktop PC solution, but it wasn't their design any more than the rest of the system they copied. There are arguments that a second button was a much better idea, but that would still not be immediately discoverable and even with many buttons in modern solutions we _still_ have double-clicking.
We also lost clearly identifiable buttons, loading bars (replaced with throbbers), status bars that tell you what you're hovering over and what the program is doing, stable UIs to develop muscle memory, etc.
But we did gain some nice things!
- Tabs.
- Titlebar buttons and other space-saving measures.
- Document editors remembering unsaved changes.
- Forms that validate on focus lost, instead of submission.
- Ctrl+P menus to fuzzy-search all actions and settings (we need more of those).
- Easy syncing (if I open Spotify on any device I'll see the same playlists, my clipboard is shared between phone/desktop/notebook, Immich integrates local and remote media, etc).
- Program-specific URL protocols, so that you can click on a link and have it open in a separate program (like `steam://open/games`).
- Map widgets, a small miracle we take for granted.
- Package managers/app stores that cleanly install and uninstall applications.
Titlebar buttons are actually bad. The titlebar exists (or existed) for a reason, so you'd have somewhere you could grab to manipulate the window. Now it's kind of a guessing game with every app on where you can grab without causing the app to do something you didn't want.
If that's a problem for you, you have much to gain with better window management shortcuts. On KDE I have the Windows key + left click set to drag a window from anywhere, and win + right click to resize depending on the quadrant the cursor is on. It's incredibly satisfying not having to hunt titlebar empty spaces or thin edges.
But do you see that title bar buttons are bad explicitly because you have to hunt for title bar edges?
That you were more or less forced to adopt these KDE shortcuts so that you could work around the fact that they had cannibalized the title bar for a purpose it was not designed for.
You were forced to change your workflow and everybody else is having to be forced to adapt because they changed a metaphor that has remained stable on the desktop for over 40 years
> You were forced to change your workflow and everybody else is having to be forced to adapt because they changed a metaphor that has remained stable on the desktop for over 40 years
All of the "positive" items I listed come with drawbacks. I didn't realize I might be in the minority for this one, since I genuinely prefer the new workflow.
My main interaction tool with the system is the pointer. Reaching out for the keyboard is something I do when I want to type, but for example when I am consuming content on my computer I just keep a single hand on the mouse or the trackpad. In that case shortcuts are just plain annoying.
On KDE, something nice is that if you have a maximized window and a panel on the top of the screen, I can drag that panel to grab the window (or maybe it was a setting of Latte dock or something). And since window titlebars nowadays can be cluttered with buttons, it is a predictable way to grab those windows only using the mouse.
fwiw, when I'm on an OpenBSD desktop, I use cwm which doesn't supply titlebars, and I use Meta+click to move windows. That's great...On OpenBSD. But sometimes I'm using a Windows computer. Sometimes I'm using a Mac.
...And sometimes I'm using OpenBSD, so titlebar buttons introduce a titlebar I didn't want, and didn't need, which doesn't match the rest of my desktop customizations.
> Forms that validate on focus lost, instead of submission.
Not always positive. The form briefly loses focus for two seconds (while you open your password manager or whatever) and you are shouted at to “PLEASE ENTER A VALID USERNAME” in red.
Sometimes I see it complaining _on every keypress_. Certainly annoying, but much better than the old "invalid field" red text at the very bottom, leaving you to scroll back up and guess what's wrong.
There is a very practical reason for this; most GUI apps are webapps (whether local or not is irrelevant), and the fetch API was so poorly thought out that it was not possible to get an indicate of progress - all if gives you is inprogress or done (nothing in between).
As a result the loading indicator can only indicate in-progress or done.
There might have been worse ways to design the fetch API, but off-hand, I can't think of any - what came before it was immensely better for a user experience.
With a better API we could have a progress bar that goes through the TCP/IP stack: advance when the domain is resolved, when a handshake is finished, when the request is sent, when the response starts streaming back, when the response finishes.
It'd be a very jumpy bar, but it helps develop intuitions. "The first part is always slower on this machine", "when it gets stuck on this spot I need to reset my router", "this part will be slow because the request is large", etc.
Most of the time you're fetching multiple things in parallel and you could show a progress of how many of those are done (perhaps weighted by estimated size). That's essentially the way many progress bars work.
> Titlebar buttons and other space-saving measures.
This has been net negative. Now everyone thinks it’s ok to shove every control up there and there’s nowhere to grab a window to move it that isn’t also a button. But the OS interprets button click and mouse drag as cancel the button click.
I wish people would stop doing this.
We HAVE HI DPI screens with large resolutions and even 640x480 had title bars!!!!!
Tabs aren't really new: look at BeOS which could "tab" windows..
That said I agree with you that tab are really nice, especially the way VSCode manage them with the vertical list of opened files (I switched from vim to VSCode due to this feature).
There was a brief moment in history where we had the best of both worlds.
I grew up with Windows XP. We had most of these (except the titlebar buttons — although on second thought some custom Windows Media Player skins did have that, haha).
We all carried USB sticks around. So you always had your files with you. The computer itself was interchangeable, for the most part. (Which also led to my interest in portable apps.)
None of the gains you list have anything to do with user interfaces. They would all or mostly be possible in any of the older desktop environments shown.
The screenshots in the post include many old applications, sometimes jarring to modern sensibilities. I think it's fair to have a discussion here about the evolution of application UI too, no?
Yes. The macOS menu bar is also searchable, which is cool. Unity on Ubuntu also had this back in the day.
Most people haven't experienced "addressable interfaces" like Emacs and don't know what they're missing when they only have visuospatial navigability. I would like to see searching and jumping make bigger impacts in mainstream UX design.
Probably! To quote William Gibson, "the future is already here — it's just not very evenly distributed". I'm sure you can find some of these features all the way back in The Mother of All Demos, the difference now is that they're more common.
One of my biggest bugbears is losing the OK/Apply/Cancel concept with dialog boxes or settings windows. If I have a window with lots of settings that I want to experiment with then I've no problem with that setting taking effect immediately, but please give me the ability to back out all the changes I've tentatively made via a Cancel button.
I have a feeling you're in the minority. I've been using computers for 35+ years and I feel like I still don't understand OK/Apply/Cancel buttons. I still click Apply before clicking OK even if I know it's unnecessary.
Plus, I don't believe Cancel reverts changes the user made if they clicked Apply already. So your suggestion would go against how the UX of OK/Apply/Cancel has historically worked.
I agree. There's something about those 80s and 90s interfaces with their visible affordances, grab points, etc., that just makes them instantly comprehensible. Many of them are also beautiful.
The absolute peak, for me, though are those early releases of MacOS X. Cheetah and Puma were both incredible, both in appearance, and in use. They looked fantastic but they still had all the affordances and comprehensibility of earlier interfaces.
One thing that's also very noticeable to me: title bars are title bars and nothing else. It's just easy to grab windows and move them, resize them, etc. Nowadays I really struggle sometimes to find a place in (what should be) the titlebar to drag a window in many application.
I'm curious - how often do you use the scrollbar? For me, almost never (or only as an indication of progress through a document). I'm scrolling only with wheel or arrows or PgUp etc.
Perhaps though this is learned behaviour from scrollbars being tiny. I'd rather have the extra screen space. The scrollbar is usually a nuisance when I accidentally touch it (touchscreen) and the page jumps away.
For scrolling large distances in large documents, that's an important use case to me. As an indication of progress is another important use case, but also as an indication to show the size of the document relative to the viewport.
When reading a document in a browser, I rely on the scrollbar to know things like: how long is it? Where am I in the document? How much of the document is on my screen right now?
This is critical for decisions like: "Should I read the whole thing?" and for building a mental map of the whole document.
I use the scrollbar to scroll between parts of the document if I need to flick back and forth quickly, say between the data and the interpretation, once I have that mental map and know where things roughly are.
For mouse users, clicking and dragging the scrollbar is the fastest and most intuitive way to scroll through a large document or list. (The scroll wheel, if you have one, is much slower.)
Until some dolt decides to build "infinite scroll" - I've seen dragging the scrollbar with the mouse cause JS exceptions to be thrown on some pages. One for the UI hall of shame.
It is very difficult for people with impaired vision to find the scrollbars, buttons et.al. on windows 11. The scrollbars are too narrow and often auto hidden. The buttons are flat and not easy to separate from normal text. Tell one window from another is also quite challenge.
Have you been unable to find a DE or a DE theme with that type of UI/UX? I haven't looked into it, since I don't have these issues and prefer a more modern look, but surely there must be options out there if that's what you want.
SerenityOS is the most well known but it's a fully custom operating system of its own. For Linux you can install the chicago95 theme (includes a widget set for GTK+3) and the b00merang GTK+4 theme (doesn't help with excess padding unfortunately, but it still has proper high-contrast 3D for the widgets and color for the headerbar. The mobile-friendly responsive UX of new GTK+4 apps actually works great with the traditional 3D look.)
I'll be honest, 1053 might be my favourite xkcd comic ever, purely because it's so encouraging of sharing knowledge and learning new things. Always excided to see the lucky 10,000 mentioned in the wild.
I really wish Windows 11 had a Windows 2000 mode. I want a grey, boxy UI, but I also want al the modern technologies Windows has introduced since—DirectStorage, D3D12, fast SSDs, device-independent pixels and vector UIs, all written directly against a Windows API that is modernised, safe, and easy to use. No React, no ads in my weather app; the only browser on my computer will be the browser itself.
Hardware features are contained in the kernel. GUI has nothing to do with them.
GUI frameworks provide features for applications to draw their UI.
A selection of numerous windows managers and desktop environments allows you to choose the best GUI shell to work in.
It is somewhat of a bazaar, with different components sometimes not fitting perfectly into each other and there's a constant migration to a best new thing, whether it's systemd, pulseaudio, wayland or pipewire, but generally things work OK and it's not like Windows today offers a significantly different experience.
No thanks, I do not want Linux. I use Linux for my home servers and at work, and I'd like to keep it that way, at arm's length.
I don't know why people suggest Linux for desktop use at the first swoop. I dislike it. I dislike how janky its various GUI desktop managers are, I dislike how edge cases that are handled straightforwardly on Windows just aren't on Linux. Things like high pixel density, different audio setups, multi-touch trackpad support, notebook battery life management, and more. The bazaar thing contributes to all of these sharp edges and jank.
> Hardware features are contained in the kernel. GUI has nothing to do with them.
What I listed aren't only hardware features; they are platform interfaces that can be programmed against to produce user-mode applications without having to muck around with kernel interfaces. In fact the less as a user or user-mode developer I have to work with the kernel, the better, and Windows provides a gigantic surface area for that.
And more importantly I dislike the sanctimony of the Linux community, I dislike the distribution and the linking model of most desktop distributions, I dislike how it is 'developers first' and not 'users first', unless a giant entity rewrites the entire user mode stack to provide a useful, straightforward, and mostly intuitive platform interface (that is, Android).
I am happy with how Windows works, I like a Windows workflow, I like developing for and on Windows, I like gaming on Windows. I've used it for 26 years and broadly have no issues with it. It is a pretty superb platform which regressed after Windows 10, and about 99% of the problems with it are user-mode frameworks and applications, thin coats of paint. Windows isn't even close to 'beyond salvation'.
The "constant migration to a new best thing" is a big problem. Once written, a program should be able to run forever, but this is only true on Windows for GUIs and on Linux only for some CLIs. Arch just recently dropped the original vi from its repos because "it no longer compiled" with stricter GCC settings, and if you want to run an older GUI, just forget about it. It's hars to blame people for only targeting the Web or Windows when those two will work forever, but on Linux you have to keep up with the endless treadmill of X11 to Wayland, GTK 2 to 3 to 4, Qt 3 to 4 to 5 to 6, pulseaudio to pipewire, etc., and if you miss just one you may as well give up.
> I really wish Windows 11 had a Windows 2000 mode. I want a grey, boxy UI, but I also want al the modern technologies Windows has introduced since—DirectStorage, D3D12, fast SSDs, device-independent pixels and vector UIs, all written directly against a Windows API that is modernised, safe, and easy to use. No React
I know that you said "no React" but you might want to try ReactOS. Of course if you don't need Windows-specific driver support Linux+Wine might suffice for your needs.
Amazing walk through memory lane, and super useful. One big omission though - starting in the early 1990s, we should be seeing some Linux desktops in there, but I didn’t see any through 1995 or so when I stopped browsing. Also, Irix would be nice to get — although I don’t recall if SGI had much in the way of custom vibes for their window managers, they certainly had amazingly cool 3D demos.
A nice vibe coding project here would be to show these in a carousel with the UI being 1:1 pixels. It’s hard to understand just how different NeXTStep (Did I capitalize that correctly?) felt from Windows — part of it was refresh rates, but part of it was going from 800x600 to 1132x800-ish on the monitor. Color, refresh rates, monitor quality, a cool plastic color and design for the box were all part of the experience.
> It’s hard to understand just how different NeXTStep (Did I capitalize that correctly?) felt from Windows — part of it was refresh rates, but part of it was going from 800x600 to 1132x800-ish on the monitor.
You can't really get it from these screenshots, but I'll give an example of what you're talking about.
I remember GEM when it came out, and it simply looked terrible. Not just their color choice, but simply that low resolution display there were stuck with in the day. It looked cheap, and like a toy. Specifically in contrast to the Mac, which, while it was a smaller monitor, and even lower pixel count, the overall display was crisper, and cleaner, brighter, better contrast.
The Amiga suffered similarly. Big and blocky and fuzzy.
Also, don't forget that the NeXT computers were striving for being "3M" computers. "3M" for 1M pixels, 1 MIPS, and "1 Megapenny" ($10,000). Definitely a different class of machines to OTS PCs of the day.
Nice. A Redhat Mother’s Day set would be amazing. I didn’t screenshot much in that era, and had a catastrophic data loss in 1998 or so that was a real bummer; Usenet, emails, IRC logs. Even then it hurt, but today, ouch.
Seeing these brought back a flood of memories. Logging onto AOL through GeoWorks for the first time. Clicking that tiny lit apartment window in the Macintosh mouse tutorial and watching the curtain peel back to reveal a couple dancing inside. Mesmerized by the soft shade on OS/2 buttons like they were works of art (yes, I know that’s weird). Bringing my NeXTstation into the office when I was just a lowly game tester and getting that look from my boss.
Invisible scroll bars are a source of constant annoyance. And it sometimes takes me several attempts to move a window, because of all the various clickable things without visible boundaries. Frustrating.
I'm on Windows and Mac. Not because I love them, but because that is where my customers are. Also I try to keep my computers fairly vanilla, so that they don't look too different to the user's computer when I do videos or screenshots of my software.
It's suprising at first look that GEM tops my preferences
but I recall having a very fond time on the Atari ST 520+.
It had one of the best b/w monitors and TOS+GEM was orderly and uncluttered.
Only preemptive multitasking and per-window menus were missing. As a plus, the OS was in ROM, so boot times were <1s.
The man behind this site is known for his skills of recoverying data from QIC tapes.
Looking at the "Software Library" section makes me always wonder if it will be released at some point, since that there is some stuff that isn't on BitSavers or other sites.
I hated magenta-blue CGA graphics soooo sooo much as a kid. It was (and still is IMHO) the ugliest thing I ever saw on a computer, by far.
I had a monitor that had a switch in the back that would change those colors to red-yellow-green. It was still awful but at least it was less awful than white-magenta-blue
It's one of my favourite things, looking at and analyzing older interfaces. Some are lovely, some are cute, some are ugly, but most are... "naïve"? I love to think about the effort, the research, the trials and tribulations. I feel I will spend a great deal of time in this page!
First and foremost to me those screenshots are somewhat disappointing as they can't match my memories. NeXT, BeOS, Irix, OpenLook, SunOS, Arthur (imagine the diversity)... they were SO awesomely impressive at insanely high multi-sync CRT resolution.
Reality simply can't match the mind's eye, at least not for me.
I was thinking exactly the same. IRIX on a great Sony CRT is still awesome to just look at, to this day (I have _few_ SGIs). HP Vue, Solaris.. the greats.
One that does seem to be an odd man out is Genera. What a concept.
For the people that didn’t live through this time, lining these images up makes it obvious why those that did speak of how visually impressive the Amiga was.
I was still in school when OS/2 came out. I read about it in the magazines never touching it myself. I was impressed with its aesthetics but never knew with the clout of IBM why it never took off. My guess is internal politics killed OS/2 more than Microsoft?
I am starting to think the top half of the screen should be the desktop, the bottom half should be the start menu but already activated and full of programs. No conventional bottom panel-bar with a start button. A right-most column should exist that fills up with a list of opened windows. [1]
When I first saw Win95 with a cleared desktop, I immediately thought - where has everything gone? Why is this empty? Decades later I still think it's cumbersome to have to look and press at bottom left to see all the programs every time.
[1] proportions and locations can be set
Also, a "sweep" button that quickly clears the desktop into a "desktop archive." I do that manually anyway with my own "sweep" folders. Every few months I delete and categorize within the sweep folder. Keeping the desktop clean and organized is the new frontier, especially as screens become smaller and people don't want to lose flow.
Verbose response, but what are your thoughts? Maybe use voice recognition that uses lip-reading through a camera to launch or modify?
Mice and keyboards are just so passe, right, but I wouldn't go so far as getting a brain chip? Maybe a spherical "touchball" that senses the pressure of each finger to move a cursor? Trackballs are too laborsome. I have my mouse on maximum sensitivity and acceleration anyway.
Screen real estate is precious unless on the very largest screens. Especially vertical. I'm a big fan of being able to put the app list/bar on the right, keeping the maximum vertical space available and allowing its captions to be readable horizontally.
> Maybe use voice recognition that uses lip-reading through a camera to launch or modify?
This feels like the result of a competition to design the worst possible user interface. To about 5% of people it might be an accessibility feature, to everyone else it's worse, and people with beards, marks, or dark skinned faces are going to find it a disaster.
True, it's not a good solution and there is Subvocal Recognition (SVR) that detects electrical signals in the neck or jaw using pads. Hall effect keyboards are pretty good in terms of sensitivity I find.
Lip reading by HAL was also a disaster for Frank Poole.
Maybe a large screen that can easily be flipped vertical/horizontal would work well. People already do it with the their smartphones - why not stationary screens? Have the OS detect when it happens so it can make any predetermined layout changes. Maybe have it rotate using a small motor? Cable connections into a base unit to avoid entanglement.
In terms of screens - I think two volume dials to adjust for brightness and another one for blue-light would be ideal. It should be super easy to do at a hardware level. On 24 hour programs if really pedantic. Maybe an external "volume dial" pad that can be plugged into a USB-C would be suffice and it could have a light and movement sensor as well to take a computer out of (and into) suspend and set the desired brightness according to the environment.
There are rechargeable closet lights that already have movement and light sensors - just need to adapt it to a screen.
> Maybe a large screen that can easily be flipped vertical/horizontal would work well. People already do it with the their smartphones - why not stationary screens? Have the OS detect when it happens so it can make any predetermined layout changes. Maybe have it rotate using a small motor? Cable connections into a base unit to avoid entanglement.
Good news: all of this except the motorization is already available from Dell and others. Common office setup. I often see people with one screen in portrait format for reading documents.
> This feels like the result of a competition to design the worst possible user interface. To about 5% of people it might be an accessibility feature, to everyone else it's worse, and people with beards, marks, or dark skinned faces are going to find it a disaster.
You say that, but I have seen in the wild a scroll gesture to increase or decrease the value of a telephone number.
Wasn't even capped at zero, so I could scroll to a negative (phone) number.
OK, does anyone actually remember if half of the systems of the 80s really had such perfect font rendering or is this just some emulation 'current version'?
The first computers I used were 486 with DOS and early Pentiums with Windows 3.11 and nothing looked nearly as nice. Some of those old screenshots look A LOT better than stuff 10 years later that I used (incl MacOS 8 or 9).
Older OSs had pixel fonts, which were carefully hand-crafted --- vector fonts were something which folks dreamed about having, or which were accessed when using incredibly expensive printers.
Font rendering on Windows 3.11 was pretty decent, so long as one used the nicer TrueType fonts --- Times New Roman and Arial had man _years_ of hinting effort by Monotype which kicked in at typically screen sizes --- that said, certain apps would still use the older pixel fonts Tms Rmn and Helv (over which Linotype sued for trademark infringement which is part of why Monotype got the contract) as well as the "vector fonts" Roman and Modern which are (one can still access them in Windows 11) stick/plotter fonts like to the Hershey fonts. When I bought my copy of Windows 3.0, I drove almost 100 miles into Richmond to get a copy of Adobe Type Manager 1.0 for Windows.
RISC OS (1987) had built-in support for anti-aliased vector fonts, though they aren't shown in the screenshot. The OS was in ROM and had insufficient space for the actual fonts so they needed to be loaded from disk. This was fine if you had a hard disk but a pita with floppies.
The monitors of the time were a lot blurrier than the screen you're looking at the screenshots on. For maximum verisimilitude you'd have to have photographs of screens.
I got an 800x600 LCD monitor in about 1999, and it was a massive upgrade.
It's a tradeoff. A 800x600 CRT will look "blurry" compared to a LCD when rendering old-style GUIs or text in a properly hinted font, but the 800x600 LCD will look blocky and pixelated when rendering a real-world photorealistic image compared to the CRT. The real look of that CRT is more like taking that old 800x600 photo and upscaling it to 1440x1080 on a modern FullHD display. Blurry to be sure, but not blocky or pixelated. Early LCDs also had terrible image persistence/ghosting issues that showed up when playing games.
No https version of this site, I configured my browser to warn or block non https websites, since from my experience few of those tried to force download (what i can only assume to be viruses) to my computer
I understand that https can do that to, but its usually the none https that does, so its a decent configuration to have
Where did the author get a copy of pre-X-integration NeWS, I wonder (if indeed they did). I haven’t been able to locate one online after a lot of determined searching, but I also can’t bring myself to declare that there isn’t one because the name is so ungoogleable.
He also got Parallax p/NeWS in his collection, which is super rare. I also wrote a person who has a SunDew QIC cassette, and another that has various NeWS sources (including the portable REF tree of the 1.1 version). Unfortunately they haven't released them yet, because of the unknown copyright situation.
Another person has the OpenWindows 1.0 binary tapes for Sun-3 and Sun-4, among other stuff.
For now we have the sources of NeWS 1.1 (and operators.h if you look more in depth) and X/NeWS 2.0. I also have the RBuss sources (an incomplete clone), but I have to ask the author if they can be put on the internet.
Can't help noticing how the interface and general mechanics of these old OSes were tightly coupled to the hardware. Both the makers and users of that era seemed to relish that vibe. I know I certainly do.
However, that paradigm made computers daunting for anyone who wasn't an enthusiast. While I’m nostalgic for that level of transparency, I recognize that those hurdles stood in the way of mass adoption.
We might lament how 'dull' or 'abstracted' modern software feels, but technology's primary purpose is utility, not just to be venerated as an artifact.
THAT SAID, I still believe that user-friendliness isn't an excuse to strip away agency.
Modern simplification shouldn't feel like a forced lobotomy of the OS (or any piece of software really). There’s no reason we can't have both: an interface that stays out of the way for the average user, while providing total control for power users.
The plan 9 interface has evolved quite a bit, but it's largely invisible in screenshots. The differences are in things like triple click behavior, jumps to insertion points, effective use of mouse cursor warping, chording.
It's funny how early some things do and don't look familiar. A decent chunk of unix-family OSs have changed some since then, but also kinda not. CDE 1.0 looks almost exactly like the latest version:)
It's nice to see some of these things and finally make out any contents! I've felt hurt by Wikipedia's somewhat odd and sad screenshot policy, which makes it impossible to see any details of the things I've been looking at recently, like early Windows NT.
The BeOS aesthetic has aged so well. I'll always wonder what might've been had they not been deliberately smothered in the crib (or at the very least if Apple had chosen to acquire them).
While I recognize many of these, I had no idea about the IBM Academic Operating System (a version of UNIX for their RT RISC workstations distinct from the normal IBM version AIX). There are just snippets of info about this OS on Wikipedia and other sites -- I wonder why IBM created it when they already had AIX.
Over time much NeWS related stuff resurfaced, wheter are application binaries, sources (both application and the server itself) or documentation, so anyone could play with them on a real machine (Sun-3 or SPARC) or inside QEMU SPARC.
I'm waiting for a copy of "Portable NeWS 1.0" to be recovered, to see how much different the sources are compared to the 1.1 version.
I also hope to see resurface binaries/sources of other server implementations, Sun Symbolic Programming Environment (which includes code originally developed at Schlumberger, including LispScript), the sources of the PdB compiler, CMU Andrew wm (although is not directly related, is the ancestor of this window system, from the same authors), and whatever is related to this system.
There is a `man` entry displayed in a terminal window there. The first Unix I've ever touched was HP-UX on an HP-9000 (server series, not the workstation one), and I have this memory that the underlined words you can see in that manpage as well were actually hyperlinks you can select and would bring you to the relevant section of the manpage that discussed that term. Am I fabricating that memory or is it real? I cannot find any info about it on the Internet.
I started with HP-UX 9.03 on a PA-RISC-powered 715-75 (to
use Emacs, our whole research group logged into the 735 server to edit there, which was faster than running it locally).
Any unclean pointer fiddling in C, and the process was terminated by the OS, so the machine was wonderful to use as a development box (especially with Purify installed) for software that would later be run on Windows or Linux.
I eventually bought my own refurbished (and using academic discount) 715 (instead of a car), so I had the fastest machine in our student dorm of anyone I knew, undergrad, grad student or professor. I could just write my Master's thesis when everyone else kept re-installing Windows - the HP never crashed in 6.5 years, which has left me with deep respect for the old-schol (pre-Compaq) HP engineers. The machine (21" color CRT) occupied half of my 9 square metre dorm room, but it also kept me warm.
In the GNU world, indeed. And that's why it makes even harder for me to remember exactly, it was 30 years ago, I was clueless and also Linux was already "big enough" to have some Red Hat installed in some x86 PC in the same lab.
Regarding Amiga screenshots, they've taken care to get the DigiPaint aspect ratios right, but the Workbench 2.04 screenshot is in a resolution that comes from an add-in graphics card rather than the Amiga's custom chips. It's a resolution Workbench wasn't graphically designed for, so it looked wrong in such a resolution at the time. If you double the screenshot's height, then everything (text, icons, window gadgets etc) looks right.
It would be more representative of the OS, and the era, to have a height-doubled "HiRes" screenshot, 640x200 or 640x256.
The aspect ratio is correct on all screenshots and are accurate de-interlaced representations of a 640x400/512 workbench setup, even though these particular screenshots are in RTG dimensions. Starting with ECS, the Amiga was also capable of true non-interlaced 640x400 output (and even 480 vertical lines unless I misremember) in what was commonly called "productivity mode", limited to 4 colors (2 bitplanes).
Interlaced workbench setups weren't uncommon. I ran such on and off for years for certain productivity stuff where I wanted more screen real estate, until I decided to spend money on a flicker-fixer.
Yes it is, was my post unclear? Following your suggestion that someone might contribute a screenshot of 1.x, which I agree would be a nice addition, I'm suggesting a "HiRes" screenshot of 2.x or 3.x would be a better representation of how it looked in-period to the vast majority of users. The point is just that the icons, text, and general UI chrome were designed for that lower vertical resolution.
I ran the interlaced modes later after buying a flicker-fixer, but didn't know of anyone who used them without one - the flicker meant those interlaced modes weren't generally considered to be very usable.
I kinda miss that in the early 2000's kde and gnome shipped with a fuck ton of window decorations based on all those (then-not-so) old OS. Teenager me had fun switching them every day and playing with windowing behavior (focus follows mouse! hover to select and only one click needed!). I wonder what techy kids today do to explore and have fun.
Speaking of the early 2000's, man, Aqua was such a good design. I appreciate the nextstep paradigm and design, but Aqua was just so futuristic, in a good way.
In some ways X11 with it's focus follows mouse, don't raise on focus, select:middle click paste features provide a far more refined desktop experience then mac or windows ever could. No wait, stop laughing, sure X11 was a garbage fire when it came to consistent professional design, but because it was such a wild west of an environment there was place for real ui innovation. I know, I get grumpy fast without middle click paste. And I hate having to raise a window in order to click and type on it(A common access pattern for me is to read docs on the top window while I am operating the bottom window).
... Is that Sinfest? From before the author went weird? If so, then that's certainly a very different way of feeling old than I expected when clicking the link.
P.S.: There's another in "RiscOS 3.71", and "System V Release 4 Amiga Version 1.1" references Penny Arcade. [0]
There's a lot of nostalgia in the comments here. I wonder if any reader under say 25 is willing to comment; do you think OS's today are a regression? do those look better?
To me they look unwieldy, heavy and overwhelming and I can't help but think the love for them is just the love for youth or whatever
There is definitely an element of nostalgia. However, a lot of earlier desktop OS GUIs do seem to be more internally consistent and with more emphasis on usability than the current crop. I think part of the issue is that things that might make sense on a phone have bled into desktop OSes, where they make a lot less sense.
I don't mean this in a dismissive way but based on your profile I'd say you're > 25. I'm curious about the perspective of someone who didn't grow up with the those os's
You have to appreciate that the nostalgia is not necessarily how these looked, but also how they worked.
Also, there's simply the reminiscing back to the era when these were out. When they were NEW, and revolutionary.
All things that cannot be conveyed from a static screenshot.
Consider NeXTStep. Something you cannot see from these images are that when you moved a window on NS, the entire window moved. Not a frame, the entire thing. This was not normal in the day. Or that NS used Display PostScript. "Not only are they moving the entire window, they're using DPS to do it!" PostScript was powerful, and expensive, and for printers. Yet, here it was.
Or how fast BeOS was, and its cool filesystem, and other aspects.
It's certainly an interesting question to ask folks that have opinions simply on the cosmetics of the various images that we see here, but appreciate that for the folks that "were there", at least for me, I'm not just remembering what it looked like, it's much more than that.
I will never forget when the Mac first came out, my friend and I went to see one at a computer store. And my friend just sat there, mouth agape, moving the mouse back and forth across the menubar, seeing them popup and popdown as it moved, and just going "Woooowwww".
You’ll need an under-25 who’s both used some of these enough to really understand them, and has watched others of mixed expertise levels use them, to get a meaningful opinion. Screenshots don’t cut it, for the same reason as why modern UIs can look slick in screenshots or a demo then be frustrating in actual use.
That person’s gonna be very rare, while lots of over-25s have that experience.
I’m > 25, but I didn’t use those OS. I started with Windows XP, then did a bit of playing around with Gnome 2 on Linux Mint. You wouldn’t call them pretty, But you never had to guess about an icon or if an interaction was possible. It was pure get things done (barring crashes and slow hdds).
Today’s OS are aesthetically pleasing, especially with the right combination of windows, but using them is a frustrating experience.
For some of these, you have to use them on the actual hardware to understand why so many of us are bummed about what we have lost. The latency of modern systems is kind of bonkers. Even though the machines were incredibly slow they feel faster than modern machines. Some musicians used Atari STs for years after they were discontinued because of the stable timing.
For others, the hardware wasn't important, but some of the functionality isn't apparent in a static screenshot. For example, I loved OS/2 and the Workplace Shell. It had functionality similar to Windows COM or CORBA in that everything on the system exposed an interface that could be easily scripted or used by other applications. The built-in scripting language was Rexx which I feel could have played the role Python does now if only OS/2 had taken off. Using OS/2 from 1.3 onwards felt like you were using a computer from the future.
Basing one's opinion on how a static screenshot looks, is the reason we've moved towards pretty looks and away from usability concerns.
As other commentors have said, the overriding concern with these older OSs was to make them as easy as possible to use. It would never have crossed these developers' minds to, for example, hide the scrollbar because they think it looks ugly.
Looking at a screenshot doesn't really tell you anything if you're not familiar with it, but it's a nice reminder of using that software for those who are.
In most of the comments here, I'm not seeing "nostalgia" or "the love for youth". I'm seeing frustration with how the carefully researched and developed principles have been forgotten.
I'm under 30 at least and I do feel nostalgia for these albeit not having used most of them. First OS I ever used must have been Windows 95. I wish we could all go back to Windows 7, that was the best OS ever imo.
I'm 23 and IMO, the Windows desktop style peaked somewhere in Windows 95-2000. The first Windows I ever used was XP, so I'm mostly making that decision based off screenshots and emulators.
UIs back then were dense, didn't waste large amounts of space in a misguided attempt to be "minimalist", and had affordances for ease of use. There was no scrollbar hiding, no animations that made the user wait for no reason other than the designer's ego, very visible borders on windows and buttons that made finding/resizing them easier, large bars at the top of windows that let you move them around, and actual text for most buttons instead of icons that are anyone's guess what they mean. Thankfully some of this can be dialed back in the Windows 11 accessibility settings, at least for missing scrollbars and getting rid of time wasting animations, but a lot of programs don't respect those.
That's right there is a good indicator for which programs care about their users. I'm using your program because I want to actually do something, not waste time watching your designers show off.
I've disabled animations on my Android phone too, and it gives an extremely noticable speedup. Menus appear right when I click them, instead of a second later as they slide into existence. Too bad iPhones just replace the slide with a fade of equal duration; disrespect for the user's time like that is yet another reason I will never buy one.
Those older GUIs didn't try to hide the filesystem hierarchy either. It infuriates me to no end when I use a new OS and have to hunt down the way to show the disk root, or filename extensions, or hidden files. MacOS was especially bad; I had to look up a freaking keyboard shortcut that I never would have found on my own. The common reason is so "normal people" can use the interfaces, but I think that's infantilizing and is why tons of Gen Z don't know what files or folders are. Most people can learn .docx means a Word document, and C:\Users\TheirName is where their files are.
(Notable shoutout, the GNOME open/save dialogs are the absolute worst. I wish distros wouldn't default to it. People will just go right back to Windows 11 because it's somehow better.)
There's some improvements possible, for sure. I'd like to see some programs put hint letters over buttons when you press a modifier like Ctrl so you can easily see what the shortcuts are. I don't know of any that do, but it'd be very useful for more complex software like drawing programs or word processors.
GEM Desktop 1.2 looks sooooooo like the ancient Apple operating systems. I first saw this on a friends' parents computer and was quite astonished why computers may look like that. I was very used to Windows/DOS back then.
I am also glad to have switched to Linux in 2004 already. Once you have been using Linux for a while, whenever I use windows I am annoyed at how slow it is. Just file copy operations alone and then billion excuses windows developers make, trying to copsplain why it is so slow. When I have to backup 30GB, I don't want an explanation why it is slow - I simply use what is faster. And that's just one advantage of many more Linux has. (I use the commandline most of the time though, so KDE and GNOME are IMO just pointless eyecandy these days.)
That Wikipedia article needs a better screenshot. Otherwise, very interesting. And DESQview/X was X Window System on DOS with pre-emptive multitasking, wow.
xfm from the first Slackware print, I really liked that file manager. But these days it fails to work. I tied many years ago to get it work but failed :(
Subsequent ones were designed by UI designers, and opinionated senior managers, who already knew how to use them, and took out usability features to make them "look nicer". This sort of worked when the opinionated manager was Steve Jobs. Most managers are not Steve Jobs.
> in some applications they seem to have taken extra steps to make it difficult to find the line to grab
Pet peeve of mine in Windows where the line is at most one pixel now. They also took away the coloured distinction between title bars for the active window, so you don't know where keystrokes are going to go.
Too many developers nowadays don't know this. On any HN discussion of UIs, I've been noticing a growing number of younger devs insisting that usability is entirely subjective (their words, not mine). It's not just that they don't know about cleverly thought-out things such as safe triangles in nested menus or all the affordances/signifiers espoused by Don Norman et al. The bigger problem is that they don't know what they don't know, and they come across as being unwilling to learn.
It does make UX discussions frustrating and meaningless when they could, and should, be interesting and a learning experience for us all.
I did not know about this, but I did notice my own menu-rage every time a submenu disappears!
You are always designing something with a target audience in mind, and the next, e.g. mobile phone will very likely be used by someone who has interacted briefly with a similar device, so you may re-use some already learnt patterns.
The very early UXs built heavily on desktop metaphors (like folders), but at this point many (and an increasing number of) people are more familiar with OS UI n-1 than a typical office setting.
So I don't think jumping to this conclusion is correct - there are well-designed software, it has just become much much cheaper to create new ones, so the average quality has necessarily went down.
I have a lot of thoughts on things like PC usability today. You're right that UX research would have heavily contributed to the design on these older systems. As computers moved from the warehouse to the living room they had to be easier to use and understand for people without CS degrees. I think it is fair to assume *some* things about what people these days are familiar with when it comes to the desktop GUI, but usability should receive more focus now even if it slightly hinders aesthetic. A friend of mine has been teaching a college program for video editing and she has students who needed her to explain what files and folders are. This is not the first time I've heard of things like this.
Smartphones and tablets have obfuscated so many basic functions and features that it is actively harming people's understanding of how to use a computer. Things like window sizing, executables, how apps know where things are, and how programs are installed. Android does allow users to peek behind the curtain more than iOS but Google has been going down the path of locking down Android. I haven't been in an elementary school classroom for like 17 years but I remember having computer lab time where we would learn how to use Windows 95/98. I think what has benefited my friends and others my age (~30) is that we grew up when computers were in the home and were usable enough for us to log in and intuit our way around but there was enough friction that made it so we would have to figure things out on our own.
With desktop OS I feel a lot of designers don't know how to use them. They grew up with phones and never use a desktop OS outside of work.
I'm afraid that the core of the problem is something far more simple and fundamental.
The people designing desktop apps today simply never learned the conventions that make desktop applications good. They grew up with smartphone apps, web apps, electron apps, games, etc.
In fact, you can observe from things like JavaFX, Flutter, WPF, etc., that the trend has long been about the ability of easily creating custom widgets like you could with Javascript (or Flash), rather than the convenience of having a library of widgets that look and feel exactly the same as every other widget in the system.
Sometimes I am starting to feel like how my dad looked many years ago when I tried to teach him how to use Windows. He simply couldn't see the window borders. With the latest designs I am reaching this point too. I am struggling moving and resizing windows because I can't tell where the border is.
Which is what? Windows natively has like 4 official looks. You can click around the 2 (!) settings programs and pop open windows for basically every framework windows has created (and deprecated) in the last 2 decades.
This was even worse in an RDP session. No drop shadows. I'm not sure who thought "everything should be flat and white" was a good idea.
It's just the old Windows 2.0 look.
At work I use 1 or 2 monitors plus the laptop screen (on Windows). At home I just use a single 55" 4K TV for my monitor and place apps center, left, right, and up top for rarely used stuff (on Linux). The desktop metaphor always wanted a big display but you're right - most Windows apps expect a full 1920x1080 for themselves.
When I was checking out the MacBook Neo a while back I was disappointed that the resolution is not natively x2 scaled. It uses fractional scaling when macOS handles fractional scaling quite poorly. I've set the resolution on my M1 MBP to 1280x800 so it was x2 scaled and clarity improved significantly. But I also sacrificed usable space because apps don't adjust, everything is just made larger.
But we did gain some nice things!
- Tabs.
- Titlebar buttons and other space-saving measures.
- Document editors remembering unsaved changes.
- Forms that validate on focus lost, instead of submission.
- Ctrl+P menus to fuzzy-search all actions and settings (we need more of those).
- Easy syncing (if I open Spotify on any device I'll see the same playlists, my clipboard is shared between phone/desktop/notebook, Immich integrates local and remote media, etc).
- Program-specific URL protocols, so that you can click on a link and have it open in a separate program (like `steam://open/games`).
- Map widgets, a small miracle we take for granted.
- Package managers/app stores that cleanly install and uninstall applications.
That you were more or less forced to adopt these KDE shortcuts so that you could work around the fact that they had cannibalized the title bar for a purpose it was not designed for.
You were forced to change your workflow and everybody else is having to be forced to adapt because they changed a metaphor that has remained stable on the desktop for over 40 years
All of the "positive" items I listed come with drawbacks. I didn't realize I might be in the minority for this one, since I genuinely prefer the new workflow.
On KDE, something nice is that if you have a maximized window and a panel on the top of the screen, I can drag that panel to grab the window (or maybe it was a setting of Latte dock or something). And since window titlebars nowadays can be cluttered with buttons, it is a predictable way to grab those windows only using the mouse.
...And sometimes I'm using OpenBSD, so titlebar buttons introduce a titlebar I didn't want, and didn't need, which doesn't match the rest of my desktop customizations.
It's just a bad paradigm.
Not always positive. The form briefly loses focus for two seconds (while you open your password manager or whatever) and you are shouted at to “PLEASE ENTER A VALID USERNAME” in red.
There is a very practical reason for this; most GUI apps are webapps (whether local or not is irrelevant), and the fetch API was so poorly thought out that it was not possible to get an indicate of progress - all if gives you is inprogress or done (nothing in between).
As a result the loading indicator can only indicate in-progress or done.
There might have been worse ways to design the fetch API, but off-hand, I can't think of any - what came before it was immensely better for a user experience.
It'd be a very jumpy bar, but it helps develop intuitions. "The first part is always slower on this machine", "when it gets stuck on this spot I need to reset my router", "this part will be slow because the request is large", etc.
This is a failure of whatever framework the web dev is leaning on instead of actually programming the computer.
It is perfectly possible to get real progress information other than yes/no. Web sites had it for years before lazy spinners took over.
We used to have the cursor indicating this in the good old days.
This has been net negative. Now everyone thinks it’s ok to shove every control up there and there’s nowhere to grab a window to move it that isn’t also a button. But the OS interprets button click and mouse drag as cancel the button click.
I wish people would stop doing this.
We HAVE HI DPI screens with large resolutions and even 640x480 had title bars!!!!!
What space could possibly need saving?
Should have been a generic window manager feature.
Web browsers had to innovate because OSes, DEs and GUI toolkits stagnated. Tabs and better sandboxing came from web the browser.
Tabs aren't really new: look at BeOS which could "tab" windows..
That said I agree with you that tab are really nice, especially the way VSCode manage them with the vertical list of opened files (I switched from vim to VSCode due to this feature).
I grew up with Windows XP. We had most of these (except the titlebar buttons — although on second thought some custom Windows Media Player skins did have that, haha).
We all carried USB sticks around. So you always had your files with you. The computer itself was interchangeable, for the most part. (Which also led to my interest in portable apps.)
This can be really annoying when I don't want to save these changes
None of the gains you list have anything to do with user interfaces. They would all or mostly be possible in any of the older desktop environments shown.
Wasn’t that in Emacs for decades?
Most people haven't experienced "addressable interfaces" like Emacs and don't know what they're missing when they only have visuospatial navigability. I would like to see searching and jumping make bigger impacts in mainstream UX design.
Plus, I don't believe Cancel reverts changes the user made if they clicked Apply already. So your suggestion would go against how the UX of OK/Apply/Cancel has historically worked.
The absolute peak, for me, though are those early releases of MacOS X. Cheetah and Puma were both incredible, both in appearance, and in use. They looked fantastic but they still had all the affordances and comprehensibility of earlier interfaces.
One thing that's also very noticeable to me: title bars are title bars and nothing else. It's just easy to grab windows and move them, resize them, etc. Nowadays I really struggle sometimes to find a place in (what should be) the titlebar to drag a window in many application.
We have lost indeed.
Ubuntu is great for resizing - alt + middle click anywhere on the window. If only other OS'es could do the same.
Not Ubuntu -specific. On all my setups alt+LMB moves, alt+RMB near any edge resizes that specific edge.
No need for pixel-perfect grabbing.
I wonder how hard it would be to make a thing for that...
Perhaps though this is learned behaviour from scrollbars being tiny. I'd rather have the extra screen space. The scrollbar is usually a nuisance when I accidentally touch it (touchscreen) and the page jumps away.
This is critical for decisions like: "Should I read the whole thing?" and for building a mental map of the whole document.
I use the scrollbar to scroll between parts of the document if I need to flick back and forth quickly, say between the data and the interpretation, once I have that mental map and know where things roughly are.
While reading, I'm dragging or wheeling.
https://learn.microsoft.com/en-us/visualstudio/ide/how-to-tr...
Almost every time. Scrolling with the mouse has bugs in Windows (focus on the active field) and fine grained scrolling is not possible with the mouse.
As much as it pains me to say it: custom Linux distros are not often deployed en masse. Especially not the ones that “look old”.
At first glance it looks like this is much more breadth over depth. Quite an array of systems here.
https://guidebookgallery.org/
• <https://ui.codexpanse.com/>
• <https://history.vpon.me/>
I'll be honest, 1053 might be my favourite xkcd comic ever, purely because it's so encouraging of sharing knowledge and learning new things. Always excided to see the lucky 10,000 mentioned in the wild.
[0]: https://xkcd.com/1053/
Hardware features are contained in the kernel. GUI has nothing to do with them.
GUI frameworks provide features for applications to draw their UI.
A selection of numerous windows managers and desktop environments allows you to choose the best GUI shell to work in.
It is somewhat of a bazaar, with different components sometimes not fitting perfectly into each other and there's a constant migration to a best new thing, whether it's systemd, pulseaudio, wayland or pipewire, but generally things work OK and it's not like Windows today offers a significantly different experience.
Windows is beyond salvation at this point.
I don't know why people suggest Linux for desktop use at the first swoop. I dislike it. I dislike how janky its various GUI desktop managers are, I dislike how edge cases that are handled straightforwardly on Windows just aren't on Linux. Things like high pixel density, different audio setups, multi-touch trackpad support, notebook battery life management, and more. The bazaar thing contributes to all of these sharp edges and jank.
> Hardware features are contained in the kernel. GUI has nothing to do with them.
What I listed aren't only hardware features; they are platform interfaces that can be programmed against to produce user-mode applications without having to muck around with kernel interfaces. In fact the less as a user or user-mode developer I have to work with the kernel, the better, and Windows provides a gigantic surface area for that.
And more importantly I dislike the sanctimony of the Linux community, I dislike the distribution and the linking model of most desktop distributions, I dislike how it is 'developers first' and not 'users first', unless a giant entity rewrites the entire user mode stack to provide a useful, straightforward, and mostly intuitive platform interface (that is, Android).
I am happy with how Windows works, I like a Windows workflow, I like developing for and on Windows, I like gaming on Windows. I've used it for 26 years and broadly have no issues with it. It is a pretty superb platform which regressed after Windows 10, and about 99% of the problems with it are user-mode frameworks and applications, thin coats of paint. Windows isn't even close to 'beyond salvation'.
I know that you said "no React" but you might want to try ReactOS. Of course if you don't need Windows-specific driver support Linux+Wine might suffice for your needs.
A nice vibe coding project here would be to show these in a carousel with the UI being 1:1 pixels. It’s hard to understand just how different NeXTStep (Did I capitalize that correctly?) felt from Windows — part of it was refresh rates, but part of it was going from 800x600 to 1132x800-ish on the monitor. Color, refresh rates, monitor quality, a cool plastic color and design for the box were all part of the experience.
You can't really get it from these screenshots, but I'll give an example of what you're talking about.
I remember GEM when it came out, and it simply looked terrible. Not just their color choice, but simply that low resolution display there were stuck with in the day. It looked cheap, and like a toy. Specifically in contrast to the Mac, which, while it was a smaller monitor, and even lower pixel count, the overall display was crisper, and cleaner, brighter, better contrast.
The Amiga suffered similarly. Big and blocky and fuzzy.
Also, don't forget that the NeXT computers were striving for being "3M" computers. "3M" for 1M pixels, 1 MIPS, and "1 Megapenny" ($10,000). Definitely a different class of machines to OTS PCs of the day.
https://en.wikipedia.org/wiki/3M_computer
Those really were magical days.
https://en.wikipedia.org/wiki/GEOS_(8-bit_operating_system) https://en.wikipedia.org/wiki/Berkeley_Softworks
https://github.com/bluewaysw/pcgeos
GEM + Ventura Publisher http://www.typewritten.org/Media/Images/ventura-publisher-1....
Viewpoint http://www.typewritten.org/Media/Images/6085-viewpoint-2.0-p...
AUX http://www.typewritten.org/Media/Images/aux-3.0.1.png
It's suprising at first look that GEM tops my preferences but I recall having a very fond time on the Atari ST 520+. It had one of the best b/w monitors and TOS+GEM was orderly and uncluttered.
Only preemptive multitasking and per-window menus were missing. As a plus, the OS was in ROM, so boot times were <1s.
https://github.com/spacestate1/cde-plasma
I had a monitor that had a switch in the back that would change those colors to red-yellow-green. It was still awful but at least it was less awful than white-magenta-blue
It's one of my favourite things, looking at and analyzing older interfaces. Some are lovely, some are cute, some are ugly, but most are... "naïve"? I love to think about the effort, the research, the trials and tribulations. I feel I will spend a great deal of time in this page!
First and foremost to me those screenshots are somewhat disappointing as they can't match my memories. NeXT, BeOS, Irix, OpenLook, SunOS, Arthur (imagine the diversity)... they were SO awesomely impressive at insanely high multi-sync CRT resolution.
Reality simply can't match the mind's eye, at least not for me.
One that does seem to be an odd man out is Genera. What a concept.
For the people that didn’t live through this time, lining these images up makes it obvious why those that did speak of how visually impressive the Amiga was.
Except missing that sock and falling down into the dog's path and understanding the concept of fighting like cats and dogs.
I just found out that the theme song is on Wikipedia.
https://en.wikipedia.org/wiki/Alley_Cat_(video_game)
Certainly it doesn't feel any easier to manage multiple windows than when we had a quarter of the screen space.
When I first saw Win95 with a cleared desktop, I immediately thought - where has everything gone? Why is this empty? Decades later I still think it's cumbersome to have to look and press at bottom left to see all the programs every time.
[1] proportions and locations can be set
Also, a "sweep" button that quickly clears the desktop into a "desktop archive." I do that manually anyway with my own "sweep" folders. Every few months I delete and categorize within the sweep folder. Keeping the desktop clean and organized is the new frontier, especially as screens become smaller and people don't want to lose flow.
Verbose response, but what are your thoughts? Maybe use voice recognition that uses lip-reading through a camera to launch or modify?
Mice and keyboards are just so passe, right, but I wouldn't go so far as getting a brain chip? Maybe a spherical "touchball" that senses the pressure of each finger to move a cursor? Trackballs are too laborsome. I have my mouse on maximum sensitivity and acceleration anyway.
> Maybe use voice recognition that uses lip-reading through a camera to launch or modify?
This feels like the result of a competition to design the worst possible user interface. To about 5% of people it might be an accessibility feature, to everyone else it's worse, and people with beards, marks, or dark skinned faces are going to find it a disaster.
True, it's not a good solution and there is Subvocal Recognition (SVR) that detects electrical signals in the neck or jaw using pads. Hall effect keyboards are pretty good in terms of sensitivity I find.
Lip reading by HAL was also a disaster for Frank Poole.
Maybe a large screen that can easily be flipped vertical/horizontal would work well. People already do it with the their smartphones - why not stationary screens? Have the OS detect when it happens so it can make any predetermined layout changes. Maybe have it rotate using a small motor? Cable connections into a base unit to avoid entanglement.
In terms of screens - I think two volume dials to adjust for brightness and another one for blue-light would be ideal. It should be super easy to do at a hardware level. On 24 hour programs if really pedantic. Maybe an external "volume dial" pad that can be plugged into a USB-C would be suffice and it could have a light and movement sensor as well to take a computer out of (and into) suspend and set the desired brightness according to the environment.
There are rechargeable closet lights that already have movement and light sensors - just need to adapt it to a screen.
Good news: all of this except the motorization is already available from Dell and others. Common office setup. I often see people with one screen in portrait format for reading documents.
You say that, but I have seen in the wild a scroll gesture to increase or decrease the value of a telephone number.
Wasn't even capped at zero, so I could scroll to a negative (phone) number.
The first computers I used were 486 with DOS and early Pentiums with Windows 3.11 and nothing looked nearly as nice. Some of those old screenshots look A LOT better than stuff 10 years later that I used (incl MacOS 8 or 9).
Font rendering on Windows 3.11 was pretty decent, so long as one used the nicer TrueType fonts --- Times New Roman and Arial had man _years_ of hinting effort by Monotype which kicked in at typically screen sizes --- that said, certain apps would still use the older pixel fonts Tms Rmn and Helv (over which Linotype sued for trademark infringement which is part of why Monotype got the contract) as well as the "vector fonts" Roman and Modern which are (one can still access them in Windows 11) stick/plotter fonts like to the Hershey fonts. When I bought my copy of Windows 3.0, I drove almost 100 miles into Richmond to get a copy of Adobe Type Manager 1.0 for Windows.
I got an 800x600 LCD monitor in about 1999, and it was a massive upgrade.
Historical workstation desktop interface screenshots - https://news.ycombinator.com/item?id=36191713 - June 2023 (55 comments)
Retrotechnology – PC desktop screenshots from 1983-2005 - https://news.ycombinator.com/item?id=15968745 - Dec 2017 (58 comments)
I understand that https can do that to, but its usually the none https that does, so its a decent configuration to have
Please consider making the site https
https://github.com/larsbrinkhoff/bagley-nottingham-tapes
For now we have the sources of NeWS 1.1 (and operators.h if you look more in depth) and X/NeWS 2.0. I also have the RBuss sources (an incomplete clone), but I have to ask the author if they can be put on the internet.
P.S: check BitSavers and Don Hopkins archives...
https://www.donhopkins.com/home/pub/
However, that paradigm made computers daunting for anyone who wasn't an enthusiast. While I’m nostalgic for that level of transparency, I recognize that those hurdles stood in the way of mass adoption.
We might lament how 'dull' or 'abstracted' modern software feels, but technology's primary purpose is utility, not just to be venerated as an artifact.
THAT SAID, I still believe that user-friendliness isn't an excuse to strip away agency.
Modern simplification shouldn't feel like a forced lobotomy of the OS (or any piece of software really). There’s no reason we can't have both: an interface that stays out of the way for the average user, while providing total control for power users.
Whatever happened to progressive disclosure?
The Plan 9 folks I've talked to are a bit shocked by this, but I preferred Inferno's GUI to plain old Rio/Acme etc.
https://www.seasip.info/AmstradXT/Counterpoint/index.html
NextStep/OSX was the only desktop OS that did not feel like a downgrade from Amiga Workbench
I also hope to see resurface binaries/sources of other server implementations, Sun Symbolic Programming Environment (which includes code originally developed at Schlumberger, including LispScript), the sources of the PdB compiler, CMU Andrew wm (although is not directly related, is the ancestor of this window system, from the same authors), and whatever is related to this system.
It would be interesting a revival like Interlisp.
There is a `man` entry displayed in a terminal window there. The first Unix I've ever touched was HP-UX on an HP-9000 (server series, not the workstation one), and I have this memory that the underlined words you can see in that manpage as well were actually hyperlinks you can select and would bring you to the relevant section of the manpage that discussed that term. Am I fabricating that memory or is it real? I cannot find any info about it on the Internet.
Any unclean pointer fiddling in C, and the process was terminated by the OS, so the machine was wonderful to use as a development box (especially with Purify installed) for software that would later be run on Windows or Linux.
I eventually bought my own refurbished (and using academic discount) 715 (instead of a car), so I had the fastest machine in our student dorm of anyone I knew, undergrad, grad student or professor. I could just write my Master's thesis when everyone else kept re-installing Windows - the HP never crashed in 6.5 years, which has left me with deep respect for the old-schol (pre-Compaq) HP engineers. The machine (21" color CRT) occupied half of my 9 square metre dorm room, but it also kept me warm.
It would be more representative of the OS, and the era, to have a height-doubled "HiRes" screenshot, 640x200 or 640x256.
Interlaced workbench setups weren't uncommon. I ran such on and off for years for certain productivity stuff where I wanted more screen real estate, until I decided to spend money on a flicker-fixer.
Yes it is, was my post unclear? Following your suggestion that someone might contribute a screenshot of 1.x, which I agree would be a nice addition, I'm suggesting a "HiRes" screenshot of 2.x or 3.x would be a better representation of how it looked in-period to the vast majority of users. The point is just that the icons, text, and general UI chrome were designed for that lower vertical resolution.
I ran the interlaced modes later after buying a flicker-fixer, but didn't know of anyone who used them without one - the flicker meant those interlaced modes weren't generally considered to be very usable.
Speaking of the early 2000's, man, Aqua was such a good design. I appreciate the nextstep paradigm and design, but Aqua was just so futuristic, in a good way.
And virtual desktops/workspaces also had that awe-effect back then. Although with multimonitor setups this faded a bit.
A recent favorite of mine is this one. Timestamp starts at the final submission being reviewed: https://youtu.be/DxEKF0cuEzc?si=mqE_2vpKDBsMWlKW&t=557
> /tmp/med_16.sixel
... Is that Sinfest? From before the author went weird? If so, then that's certainly a very different way of feeling old than I expected when clicking the link.
P.S.: There's another in "RiscOS 3.71", and "System V Release 4 Amiga Version 1.1" references Penny Arcade. [0]
[0] https://www.penny-arcade.com/comic/2005/01/05/the-merch#
To me they look unwieldy, heavy and overwhelming and I can't help but think the love for them is just the love for youth or whatever
Also, there's simply the reminiscing back to the era when these were out. When they were NEW, and revolutionary.
All things that cannot be conveyed from a static screenshot.
Consider NeXTStep. Something you cannot see from these images are that when you moved a window on NS, the entire window moved. Not a frame, the entire thing. This was not normal in the day. Or that NS used Display PostScript. "Not only are they moving the entire window, they're using DPS to do it!" PostScript was powerful, and expensive, and for printers. Yet, here it was.
Or how fast BeOS was, and its cool filesystem, and other aspects.
It's certainly an interesting question to ask folks that have opinions simply on the cosmetics of the various images that we see here, but appreciate that for the folks that "were there", at least for me, I'm not just remembering what it looked like, it's much more than that.
I will never forget when the Mac first came out, my friend and I went to see one at a computer store. And my friend just sat there, mouth agape, moving the mouse back and forth across the menubar, seeing them popup and popdown as it moved, and just going "Woooowwww".
That person’s gonna be very rare, while lots of over-25s have that experience.
Today’s OS are aesthetically pleasing, especially with the right combination of windows, but using them is a frustrating experience.
For others, the hardware wasn't important, but some of the functionality isn't apparent in a static screenshot. For example, I loved OS/2 and the Workplace Shell. It had functionality similar to Windows COM or CORBA in that everything on the system exposed an interface that could be easily scripted or used by other applications. The built-in scripting language was Rexx which I feel could have played the role Python does now if only OS/2 had taken off. Using OS/2 from 1.3 onwards felt like you were using a computer from the future.
As other commentors have said, the overriding concern with these older OSs was to make them as easy as possible to use. It would never have crossed these developers' minds to, for example, hide the scrollbar because they think it looks ugly.
Looking at a screenshot doesn't really tell you anything if you're not familiar with it, but it's a nice reminder of using that software for those who are.
In most of the comments here, I'm not seeing "nostalgia" or "the love for youth". I'm seeing frustration with how the carefully researched and developed principles have been forgotten.
UIs back then were dense, didn't waste large amounts of space in a misguided attempt to be "minimalist", and had affordances for ease of use. There was no scrollbar hiding, no animations that made the user wait for no reason other than the designer's ego, very visible borders on windows and buttons that made finding/resizing them easier, large bars at the top of windows that let you move them around, and actual text for most buttons instead of icons that are anyone's guess what they mean. Thankfully some of this can be dialed back in the Windows 11 accessibility settings, at least for missing scrollbars and getting rid of time wasting animations, but a lot of programs don't respect those.
That's right there is a good indicator for which programs care about their users. I'm using your program because I want to actually do something, not waste time watching your designers show off.
I've disabled animations on my Android phone too, and it gives an extremely noticable speedup. Menus appear right when I click them, instead of a second later as they slide into existence. Too bad iPhones just replace the slide with a fade of equal duration; disrespect for the user's time like that is yet another reason I will never buy one.
Those older GUIs didn't try to hide the filesystem hierarchy either. It infuriates me to no end when I use a new OS and have to hunt down the way to show the disk root, or filename extensions, or hidden files. MacOS was especially bad; I had to look up a freaking keyboard shortcut that I never would have found on my own. The common reason is so "normal people" can use the interfaces, but I think that's infantilizing and is why tons of Gen Z don't know what files or folders are. Most people can learn .docx means a Word document, and C:\Users\TheirName is where their files are.
(Notable shoutout, the GNOME open/save dialogs are the absolute worst. I wish distros wouldn't default to it. People will just go right back to Windows 11 because it's somehow better.)
There's some improvements possible, for sure. I'd like to see some programs put hint letters over buttons when you press a modifier like Ctrl so you can easily see what the shortcuts are. I don't know of any that do, but it'd be very useful for more complex software like drawing programs or word processors.
edit: typo
I am also glad to have switched to Linux in 2004 already. Once you have been using Linux for a while, whenever I use windows I am annoyed at how slow it is. Just file copy operations alone and then billion excuses windows developers make, trying to copsplain why it is so slow. When I have to backup 30GB, I don't want an explanation why it is slow - I simply use what is faster. And that's just one advantage of many more Linux has. (I use the commandline most of the time though, so KDE and GNOME are IMO just pointless eyecandy these days.)
https://en.wikipedia.org/wiki/DESQview
But using only one level of library to draw on the screen "is so lame'. /s