Amiga Screens: Looking back and the visual revolution of the future

Amiga's Copper list is the great-grandmother of modern GPU synthesizers-something that was done with 3.58 MHz in 1985, and in 2025 it is still burning 1000 times transistors to run the same logic.

The first time I dragged the Workbench screen title bar in WinUAE to fully expose the Deluxe Paint 3 below, my finger hung over the mouse without moving. It's not nostalgia. Shocking: This thing is smoother than my current Hyprland, which runs on a 5.8 GHz, 24-core, independent video memory machine. Amiga has no concept of a "window manager". It only has a screen --a complete set of bit planes, color palettes, resolutions, and scan line interruptions are exclusive to each task. You want to cut the task? Drag it down. The hardware cuts the register in the scan line gap, with zero copy, zero tear, and zero delay. What Jay Miner engraved on the chip at that time was not "multitasking", but "visual priority".

This is interesting. Amiga's "screen" is not a virtual desktop, nor is it a "workspace" in the modern sense. It is a hardware slice of physical display resources . An A500 can hang four completely different screens at the same time: 640×256 16-color Workbench, 320×200 32-color games, 640×512 4-color word processing, and even interlaced 720×480 video overlay. Each screen has its own Copper list-a string of microcode that says "Wait for scan line Y, write register X." Denise video chips execute line by line, not occupying CPU cycles. You drag the title bar down in Workbench, change the Copper list pointer, and the next frame cuts to Deluxe Paint's palette and resolution. The monitor sync signal is still intact.

Compare your contemporaneous opponents. In 1985, IBM PC/AT ran DOS, exclusive to full-screen. To cut tasks, you had to save video memory, reprogram VGA registers, and refresh the color palet-either flash the screen or as slow as a slide show. Windows 1.0 to 3.1 is still a collaborative software rendering. GDI draws to memory bitmaps and then BitBlt to frame buffers. There is no hardware layer, no scan line synchronization, and tearing is the norm. Not to mention Macintosh Plus, it is 512×342 monochrome and does not even have a color palette. Amiga has achieved preemptive visual multitasking: each screen has its own resolution, color depth, and refresh rate, and switching is completed during the vertical blanking period, and users perceive it as "instant." This is not a victory for software architecture, it is burning synthetic logic into silicon .

The opposite side will say: Amiga is dead, Commodore went bankrupt in 1994, OCS/ECS/AGA are all dead ends, and the modern graphics stack has nothing to do with it. This is half true. Commodore did break its good cards-management did not understand technology, marketing positioning was wavering, R & D budgets were cut, and AAA chipsets were difficult to produce. But thoughts are not dead . Jay Miner left Atari to work as Amiga in 1982 and went to 3dfx in 1994. His students and colleagues left NVIDIA, ATI, Intel, and SGI. The direct descendant of the Copper list is the Display List ; the descendant of the bit plane is the texture layer/synthesis layer ; and the descendant of the scan line interruption is the VBlank sync/explicit fence . Mac OS X introduced Quartz Composer in 2001, Windows Vista in 2006 DWM, Linux in 2016 Wayland-all using more complex software stacks and more expensive hardware to rewrite the 1985 set of "each line of scanning determines what to display" logic. The only difference is: Amiga uses fixed-function hardware for synthesis, while Hyundai uses programmable GPU for synthesis. The essence has not changed.

There is a front-end engineer, let's call him Xiaolin, who was adjusting a Bug in the z-index stack context last year. There are three layers of Portal in the React component tree. Each layer creates an independent DOM tree to mount to the body. The CSS isolation fails, the pop-up window penetrates the mask, and the mask blocks Toast. He added createPortal, changed z-index: 9999, used isolation: isolate, and even manually moved appendChild to #root in useEffect. It took two days. In the end, it was discovered that a third-party UI library secretly hung a Shadow DOM outside ReactDOM.createRoot. The browser synthesizer synthesized it by layer, and the Stacking Context tree did not match the React Fiber tree. Sitting in his chair and staring at DevTools 'Layers panel, he suddenly remembered a sentence a college elective teacher had read: "There was no z-index in the Amiga era, only Copper list order." He was stunned for a moment. Browser compositors (Chrome's Viz/cc, Firefox's WebRender, Safari's Core Animation) are essentially re-running the Copper list every frame : traverse the layer tree, generate draw instructions, submit the GPU, etc. VBlank flip. The difference is that Amiga's lists are static, deterministic, and executed by line ; modern lists are dynamic, dirty rectangular optimized, and committed by frame . Kobayashi has never seen the real Amiga, but he deals with Copper's ghosts every day-except that the ghosts now live in GPU drives and wear "explicit sync","dmabuf", and "SurfaceFlinger" vests.

This is the motif of tools reshaping people. In the mind of Amiga programmers, the "screen" is a first-class citizen -when you design the UI, you have to think: Is this palette enough? Will the resolution collapse? Is the Copper command enough for the next line? They regard "visual resources" as scarce goods and carefully calculate them. Windows programmers are accustomed to GDI/GDI+/WPF/Direct2D. "Windows" are first-class citizens -Resolution, color depth, and DPI are all runtime queries and dynamically adapted. Anyway, the CPU is fast, the memory is large, and the synthesizer is at the bottom. Mobile is more extreme: iOS/Android programmers don't want to synthesize at all, "Layer/Surface" is a first-class citizen --Auto Layout calculates the frame and hands it over to Core Animation / SurfaceFlinger, GPU synthesis, I don't care about the scan line. Three generations of tools have created the intuitive boundary of three generations of programmers. Amiga programmers instinctively break up animations into Copper instructions; modern front-ends instinctively break up animations into transform: translateZ(0) mandatory layers. As the tools change, the person's mental model changes-but the core constraint remains unchanged: The scan line waits for no one.