I love the screen concept, but the different resolutions and colour depth are the weakest reason for them on modern hardware.
I love the screen concept, but the different resolutions and colour depth are the weakest reason for them on modern hardware.
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.
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.
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.
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.