Comment by sam1714 | Hacker News Reader

Comment by sam1714 | Hacker News Reader

Parent Full thread

I think there's a difference between concept and the implementation. I see screens as simply compositing. Different regions have different resolutions and color depths and you use display hardware to combine these together. For modern personal computers, we got this in Windows Vista and OS X 10.0.

Circa 1985 hardware has significant limitations and it's leaking through abstractions both ways. A modern program supporting deep color writes to an array consisting of R16G16B16A16 values, next to a legacy program writing R8G8B8 and even a window with 10-bit 4:2:0 YUV HDR video. On the Amiga, the hardware leaks through by having to deal with separate bit planes and palettes.

Similarly, the 3D hardware in a modern GPU easily upscales a legacy application's surface 1.25x to handle the mid-DPI laptop screen I'm using right now. 1985 hardware can't do that, because you're fiddling with the DAC output, you can only have one screen/ViewPort scan line, no overlapping regions, and if you look carefully, blank lines between regions for the hardware to reconfigure.

Yes, but my point is that while the resolution / colour change was one aspect of screens, it wasn't really the most interesting one. We relied heavily on screens also for e.g. productivity applications that didn't have a particularly compelling reason to change either.

Many applications had settings to run either in windows on the Workbench screen, or on a separate screen. Some would then let you choose between windows on a separate screen or running effectively full-screen. And using screens like a grouping mechanism like that was overall the more common use of screens other than for e.g. paint applications that needed the different colour modes.

It felt like a less offensive version of Windows MDI concept.

It's not that there are no applications today that approximate it because there absolutely are. It's more that on AmigaOS this was ubiquitous and expected and you didn't need to do anything to fullscreen these applications - only small utilities tended to lack options to run on their own screen.

In later versions of AmigaOS, you could also open "public" screens that like the Workbench screen allowed windows from multiple applications on the same screen, somewhat like virtual desktops, but that somehow felt less compelling, I think because you then relied on separately starting multiple applications.

Ah I understand what you're saying. That was the only way to multitask on the Mac on System 5 and 6. Even with System 7, using the _hide others_ option was common, which is still there today.

Even on big screens, I like MacOS's two level cmd-` to cycle between windows in the same app and cmd-tab to cycle between apps, and App Expose (4 fingers down on the trackpad). I know what I want to find is in another browser window or spreadsheet window.

Running full screen when the apps you're using does sensible things in full screen mode works reasonably well on OS X - I use OS X for one of my clients, and live mostly in iTerm2 and browsers. It still feels different, but, yes, it's close to what I'm after. On my Linux box, I'm chasing moving that functionality into my wm, instead of needing my terminal etc. to support it - since it means I can mix and match apps and switch between floating and tiling + opening/closing screen-like virtual desktops.

I honestly don't know what will feel ergonomic on a modern setup - I'm chasing nostalgia in part, but at the same time I'm fully aware that I remember it with very rose-tinted glasses, so I'm trying to stepwise approach some mix of the nostalgic elements that works with my existing setup.

Reply on news.ycombinator.com