What do we remember when we look at an old computer?
Looking at retro computers brings back more than the shape of a device. The relationship with it enters the picture too: waiting for a program, reusing the same disk, or learning a game through experiments. Today’s tools let us do more with greater technical capacity. Older machines nevertheless remind us that processor power alone is an incomplete way to describe our relationship with technology.
My own computer journey began in 1986 and continued through the ZX Spectrum, C64, Amiga and PC. Today I use both PC and Mac. I have written separately about my ongoing journey since 1986. Here I want to consider changing habits, rather than list dates for buying particular models or invent a specific gaming memory. The history of our devices also intersects with the history of how we use our attention.
The shape of waiting has changed
Waiting for a program to load from a cassette, floppy disk or another storage medium had a different rhythm from waiting for a modern page. Of course, older computers were not all used alike; the experience depended on the hardware and software. Still, when a task involved a visible period of preparation, beginning it could feel like a distinct event. That threshold is often shorter now, while more activities remain open simultaneously.
I do not want to turn this into a universal claim that people used to be more patient. Slowness was not always educational; sometimes it was simply slow. The more interesting question is what we do with the space gained when a wait disappears. Opening another tab while something finishes is now easy. We may save time while dividing our attention more widely. Keeping the benefit of speed while reducing simultaneous commitments is one way to learn from an older rhythm without trying to return to it.
An illustration inspired by discovering older games; not an actual game screenshot.
Limited space made certain choices visible
When storage space was tight, deciding which file to keep was a more obvious choice. Capacity has grown, and files now spread across devices and services. As keeping something becomes easier, organising it for later retrieval can be postponed. Folders accumulated under the thought “It might be useful” may sound familiar. The issue is not merely the number of files, but knowing which is current, which is an editable source and which is a temporary output.
We do not need to restore old limitations to recover that visible choice. Separating a project’s source from its delivery file, keeping a clear version, and checking that an important file reopens remain useful practices. Keeping and preserving are different tasks. Seeing that a file exists is not the same as knowing you can use it when needed. Plenty of storage does not remove that distinction. It may simply allow us to postpone noticing it until the moment retrieval matters most.
Looking beyond the specifications of the C64 and Amiga
The Computer History Museum’s 1982 timeline records the introduction of the Commodore 64 and its 64 KB of memory. Its 1985 entry describes the Amiga 1000’s notable audio and visual capabilities among the personal computers of its period. Those details provide historical context; they do not establish my personal ownership dates or the exact models I used.
Specifications help explain the conditions in which people created things. They do not fully explain why a machine remains memorable. The movement of a small image, the character of a sound, and the balance between what a game shows and what it leaves to the imagination also matter. That leads to a useful question today: should we add a detail merely because we can? Sometimes a technical constraint becomes a design choice. Simplicity can be meaningful even when hardware no longer makes it compulsory.
Learning a game: discovery and explanation
There is a particular pleasure in finding out a game’s rules through action. What happens when you collide with something? How long does a move take? Which risk is worth trying? That kind of discovery remains valuable. Leaving every uncertainty to the player, however, is not automatically a respectful tribute to older games. An unclear control, unreadable text or a screen with no obvious way back creates a different kind of difficulty.
The distinction I care about is what the player is being asked to discover. Figuring out strategy can be interesting; hunting for the pause button is usually an avoidable obstacle. When considering the Rivunox project, retro inspiration should not be treated only as a visual sign. Its relationship with present-day screens and controls needs separate thought. An idea borrowed from an earlier period deserves to be reconsidered in the conditions where someone will actually use it now.
From understanding a machine to understanding a setup
An older system could bring a person into more direct contact with a file’s location, the order of an operation, or the limits of a device. Modern tools handle many such details in the background. That is a real convenience. Yet when something behaves unexpectedly, knowing what happens locally and what depends on another service still matters. A detail that became invisible may have to become visible again at precisely the moment something goes wrong.
Instead of trying to understand the entire inner structure of every technology, a more realistic aim is to know the boundaries of your own setup. Where is the original file? What keeps working without a connection? Which records disappear when an application is removed? These questions are not just demonstrations of technical knowledge. They help make your own work understandable. The account of building SeTRoX.com also connects the visible page with the arrangement that keeps it available.
PC and Mac need not be a finish line
A list of past computers can make the last device look like a final conclusion: earlier systems have been left behind, and the correct machine has finally been found. Using PC and Mac together reminds me that the path need not be so linear. The task, the required tool and the way a file needs to be accessed can all differ. Appreciating one platform does not require ignoring every useful role for another.
This is helpful when considering a new tool too. Asking “What does this task need?” before “Which is better?” makes the comparison more concrete. Opening the same file, retaining an editable source, producing a suitable output and returning to the work later may matter more than a general ranking. A brand can create a feeling of belonging. Everyday work, however, is often shaped by smaller questions of compatibility, continuity and whether a particular arrangement actually helps with the task in front of us.
AI can be a new tool for an older curiosity
Describing an idea and seeing a draft is a different way of working from many earlier computing experiences. Trying to understand what has appeared still expresses a familiar curiosity. When AI suggests an interface, there is value in asking why you like it. When it produces code, its behaviour needs observation. When it creates an image, its relationship with the topic deserves consideration. The speed of the tool does not remove the need to evaluate the result.
I do not think the useful lesson of retro computing is that everyone should work as they once did. Perhaps the thing to preserve is a refusal to treat the machine only as a box of ready-made results. Where does an idea begin? remains a relevant question with new tools. Curiosity, a small experiment and an attempt to understand what happened can connect otherwise very different periods. The gestures survive even when the interface makes them look unfamiliar.
From older files to today’s project archive — an AI-generated illustrative scene.
Leave today’s archive understandable tomorrow
Imagine returning to an old file after several years. Its name is familiar and the folder is intact, but the application needed to open it is hard to remember. Perhaps only the final image remains and the editable source has disappeared. Or the source exists but depends on a missing font or another file. This need not be a problem exclusive to old computers. A drawing, article or game draft made today can encounter the same uncertainty. A convenient tool does not guarantee that its files will remain self-explanatory.
A short project note can help: which file is the original, what edits it, and where is the shareable output? A preview image can make the purpose easier to recognise. This need not become a detailed museum catalogue. Leave enough information for your future self to understand it, then reopen an important delivery to check it rather than relying on a tidy filename alone. What deserves preservation is not merely a collection of bytes but the ability to make sense of them.
This also offers a path between deleting every old file when a new version appears and keeping everything without distinction forever. Knowing which material is an editable source, a temporary build, or an actual delivery makes the choice more deliberate. The selectiveness recalled by older machines can survive inside today’s much more comfortable tools.
What should we carry forward?
We do not have to turn every historical inconvenience into a fond memory. Long waits, lost files and opaque operations are not things to request again. Beginning a task deliberately, knowing what you keep, wondering about a tool’s limits and being willing to try a small idea remain valuable. Preserving those habits does not require owning old hardware. There can be room for them in a contemporary working setup.
Seen this way, nostalgia becomes a tool for comparison. Old does not automatically mean better; new does not automatically mean more meaningful. Each period makes something easier while allowing something else to recede from view. The question is which habits we want to keep. As machines change, we can continue asking what we are trying to do with them. That may be one of the most enduring parts of a long relationship with computers.
Let’s leave a thought here.
Sometimes the next step is to pause and look again.