Every computing platform has its party trick — the thing devotees can't stop explaining and outsiders can't quite grasp. For Amiga users, it's screens. Not monitors, not windows, not desktops — screens, a display concept so tightly married to the hardware that explaining it requires explaining the machine. This piece by datagubbe.se finally does that work properly, and the result is a small, satisfying act of technical writing. The core insight is architectural: the Amiga's custom chipset (OCS) let programs open independent display areas with different resolutions and color depths, overlay them, drag them past each other, and switch between them instantly — all on a 7 MHz machine in 1985. This wasn't a windowing system bolted on top; it was a hardware capability exposed directly to the user. The copper co-processor worked in lockstep with video rendering, changing color registers per scanline, combining playfields of different bit depths on the fly. The article explains planar graphics, indexed palettes, bitplane math, HAM mode, and Extra Half-Brite without ever losing the thread of why any of this matters to the user experience. What makes the piece work is its honesty alongside its enthusiasm. The author freely admits that screen dragging — the Amiga demo move par excellence — is of "limited" practical usefulness in actual workflows. Full-screen switching was faster and less cumbersome. The spectacle was real, the utility was modest. That kind of candor earns trust for the moments when the author does get genuinely excited, like describing how a game could display 64+ simultaneous colors by assigning different 32-color palettes to different screen regions, then layering copper gradients on top. The technical exposition is clean. Bitplane math is illustrated with the original Amiga Hardware Reference Manual diagram. The relationship between resolution, color depth, and memory is made concrete: a text editor on a 2-color screen frees RAM for a paint program on a 32-color screen, because planar graphics stores exactly the bits needed per pixel and no more. The connection between hardware constraint and OS design philosophy — preemptive multitasking on a machine with shared RAM — comes through without the author needing to spell out the lesson. The embedded video demonstration, filmed off a real Amiga 600, does what no amount of prose can: it shows the speed. Music playing, text editor open, Deluxe Paint running, screens dragging and switching with zero perceptible lag on hardware clocked at 0.007 GHz. The article earns its show-don't-tell moment because it spent the preceding sections building the reader's understanding of what's actually happening at the hardware level. The piece cuts off mid-sentence at "dual playfields," which is either a truncation artifact or a deliberate cliffhanger for a follow-up. Either way, the primer accomplishes its stated goal: it converts the vague Amiga-fan refrain of "but the screens!" into a concrete, mechanically grounded explanation that a non-Amiga user can actually follow. It's a niche topic handled with craft.
