Live data from Hacker News

Screenshots of Old Desktop OSes

typewritten.org

161–170 of 407 posts

Re: Screenshots of Old Desktop OSes

#161
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

Please consider making the site https

Re: Screenshots of Old Desktop OSes

#162
post #75

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.

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

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.

Re: Screenshots of Old Desktop OSes

#163
post #75

Earlier quoted context omitted.

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

> loading bars (replaced with throbbers) 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…

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.

Re: Screenshots of Old Desktop OSes

#164

I'm sure someone reading this thread has UAE handy in order to contribute a screenshot of AmigaOS/Workbench 1.x.

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

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.

Re: Screenshots of Old Desktop OSes

#165
post #37

I miss the old days. Thirty years ago, 64MB of RAM was considered a thing ( http://www.typewritten.org/Media/Images/winnt-4.0-ppc-new.in... )

Wait till you see the UI the Amiga could run in 1 measly MiB of RAM. You could even run a sophisticated shell, multitasked along with everything else.

Re: Screenshots of Old Desktop OSes

#166

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.

You want Linux. 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…

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.

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).

An OS is more than the kernel. It is the entire platform including user-mode libraries, toolkits, and applications. For all its faults, I find the Windows platform better than any Linux distro platform, except one.

> 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.

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'.

Re: Screenshots of Old Desktop OSes

#167
post #49

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

[deleted]

Re: Screenshots of Old Desktop OSes

#168
post #75

Earlier quoted context omitted.

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

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.

Re: Screenshots of Old Desktop OSes

#169
post #99
post #49

Earlier quoted context omitted.

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

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

> safe triangles in nested menus

I did not know about this, but I did notice my own menu-rage every time a submenu disappears!

Re: Screenshots of Old Desktop OSes

#170
post #160
post #49

Earlier quoted context omitted.

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

‘Took out usability features to make them "look nicer"’ is exactly how Steve Jobs gave us the double-click, undiscoverable and timing-sensitive.

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.
Post reply on HN