A modern Amiga revival: the next Amiga must be built for a new generation

The most Apple-like feature of the Mac is not the graphical user interface. It is not the case design, the menu bar, the startup sound, or even macOS itself. The Mac’s most Apple-like feature is stranger and more important: Apple has repeatedly been willing to abandon its own past without fully betraying the people who invested in it. Across four decades, Apple has moved the Mac through changes that could easily have killed it. Motorola 68000 to PowerPC. Classic Mac OS to Mac OS X. PowerPC to Intel. Intel to Apple Silicon. Old software frameworks retired. 32-bit applications dropped. Ports removed. Behaviours changed. Entire assumptions about what a Mac was supposed to be were replaced. It did not simply preserve the old machine in glass. It moved the platform forward, even when that meant admitting that yesterday’s Mac could not carry tomorrow’s Mac. That is the lesson a serious future owner of the Amiga legacy should study closely. At some point, moving on becomes the respectful thing to do.

The past is not a product strategy

The Amiga has one of the most remarkable stories in personal computing. In the mid-1980s, it made colour, sound, animation and multitasking feel natural at a time when much of the computer market still felt stiff, monochrome or business-first. It attracted people who wanted to create: musicians, video artists, game developers, demo coders, designers, hobbyists and technical experimenters.

That is why the name still has weight. It is why people still repair the machines, collect the software, argue about the operating systems and build new hardware around the old idea. The Amiga was not just a computer. It was a feeling: immediate, creative, technically elegant and unusually close to the user. But history is not a product strategy.

A museum can preserve the past. A platform has to create the future. A new Amiga can and should do both, but it cannot confuse one job with the other. Classic Amiga software should be protected, made accessible and treated as part of computing culture. But a future Amiga cannot be designed as if every old program, every old behaviour and every old hardware assumption still deserves a vote. That would not be loyalty. It would be paralysis.

The world does not need another Windows clone

The case for a new Amiga becomes more interesting when it is pulled away from nostalgia. The world is not short of computers. It is not short of operating systems either. What it lacks is a credible alternative to the two dominant stories in personal computing.

Microsoft represents the corporate standard: familiar, powerful, widely supported and deeply embedded in business life. Apple represents the controlled premium ecosystem: polished, integrated, attractive and increasingly closed. Both have strengths. Both have millions of satisfied users. But between them, personal computing can feel like a choice between administration and obedience. That is where a modern Amiga would have to find its argument.

It should not try to beat Microsoft and Apple at their own game. It should not become a cheaper Windows machine, a weaker Mac, or a Linux distribution with nostalgic wallpaper. That would be a dead end. The opportunity is not to imitate the giants. It is to offer a third language: personal, creative, understandable, privacy-conscious and open enough for the user to feel ownership again.

This should not be sold as romantic rebellion. It is a market position. A smaller platform does not need to conquer the whole world to matter. It needs a clear audience and a reason to exist. A future Amiga should not promise to replace Microsoft or Apple. It should promise something they no longer offer very well: a computer that feels personal, creative and understandable. A system where the user is not merely a customer inside a managed ecosystem, but the active owner of the experience.

Privacy could be the new killer feature

A new Amiga OS would arrive in a very different world from the original machine. The fight is no longer only about graphics, sound or multitasking. The modern fight is also about control.

Many users are tired of accounts, telemetry, forced app stores, subscription pressure, cloud nudges, advertising profiles and operating systems that behave as if the user is only borrowing their own computer. The machine has become smoother in many ways, but less personal in others. It asks people to sign in, sync, accept, subscribe, update and trust. Too often, the computer seems to serve the platform owner before it serves the person sitting in front of it. That creates an opening.

A future Amiga OS could make privacy and ownership central to its identity. Not as a slogan hidden in a settings menu, but as a visible product promise. Local-first by default. No forced account to use the machine. No silent data collection. No mandatory app store gatekeeping. No constant pressure to move personal files into someone else’s cloud. Updates that serve the user instead of interrupting them. Apps that ask clearly, behave honestly and can be removed cleanly.

This is not only a technical position. It is emotional and practical. People want powerful machines, but they also want machines that respect them. In a market where computers increasingly behave like service terminals, ownership itself could become a feature. A new Amiga OS should treat privacy as a design principle, not a marketing badge. The user should be able to start the machine, create work, install software, store files and use local tools without being pushed into tracking, subscriptions, accounts or cloud dependency. The message should be simple: this is your computer, your data, your work and your choice.

Do not build it for the old guard

There is a difficult truth here. A future Amiga should respect the old Amiga community, but it should not be designed mainly for them. The old guard kept the name alive. They repaired the machines, archived software, maintained forums, built accelerators, defended the culture and kept using the system long after the wider industry moved on. Without them, the Amiga would be a weaker memory. But they are also likely to be the hardest audience to satisfy.

Long-time Amiga users do not all want the same thing. Some want perfect compatibility. Some want old behaviours preserved exactly. Some want a Workbench feeling. Some want PowerPC continuity. Some prefer FPGA purity. Some want a machine that feels like their favourite moment in Amiga history. Each wish is understandable. Together, they form a trap.

A serious new Amiga cannot be built around pleasing every memory. The target has to be a new generation: young creators, independent developers, musicians, video makers, students, privacy-conscious users and people who feel trapped between corporate Windows and controlled Apple ecosystems. The old users should be welcomed. Their knowledge matters. Their criticism may often be useful. But they cannot be allowed to define the ceiling.

The future Amiga has to make sense to someone who never owned an A500, never used Workbench and has no emotional investment in Commodore. If that person can sit down, understand the idea, create something and feel that the machine has a different attitude, then the Amiga legacy has genuinely survived. The old guard can validate the roots, but the new generation must validate the future.

The Amiga spirit was never just the old hardware

One of the most important mistakes to avoid is confusing the Amiga’s spirit with its original technical limits. The soul of the Amiga was not a specific chipset, screen mode, processor or file requester. Those things mattered, but they were tools of their time.

The deeper Amiga idea was immediacy. The machine felt close to the user. It made graphics, sound and motion accessible. It invited experimentation. It made the computer feel less like a business appliance and more like a studio, playground and workshop. That idea can still be modern.

A twenty-first-century Amiga should ask what immediacy means now. Low-latency audio. Fast visual tools. Simple local creation. Clear file handling. A clean development environment. Transparent system behaviour. A desktop that does not bury every action under cloud services, subscriptions and permission prompts. That would be more Amiga-like than simply redrawing old icons.

BSD could be the quiet engine underneath

Writing a completely new operating system from scratch sounds heroic, but it would probably be one of the most unrealistic choices a future Amiga owner could make. A modern OS is not just a desktop and a file manager. It needs memory protection, networking, security, drivers, filesystems, hardware support, developer tools, accessibility, package management, update systems and years of maintenance. Starting from zero would turn the new Amiga into a research project before it ever became a product.

A more credible route would be to use BSD as the core. BSD is mature, clean, flexible and proven in serious commercial and consumer systems. Sony’s PlayStation software stack, for example, has drawn from FreeBSD technology, and Apple itself built macOS on a Unix foundation with BSD heritage. That does not mean a BSD-based Amiga would be derivative. It means it would be realistic.

Most users do not fall in love with a kernel. They respond to the experience above it: how the system starts, how fast it feels, how it handles files, how apps behave, how clearly it communicates, how well it protects privacy and whether the machine feels like it belongs to them. BSD could provide the floor. Amiga could provide the room. A new Amiga OS should not waste years trying to invent every layer from scratch. BSD could provide the stable, proven core, while the Amiga identity lives in the experience above it: fast, local-first, creative, private, understandable and personal. The kernel should be the foundation, not the brand.

Do not rebuild the custom-chip dream

The same realism applies to hardware. A future Amiga should not try to recreate the old custom-chip miracle by building a new revolutionary OCS, AGA or Paula for the modern age. That battle is over. In the 1980s, custom chips gave the Amiga a real advantage. The rest of the market was still catching up with graphics, sound and multimedia. The Amiga could feel magical because its hardware was designed around those abilities from the start.

Today, trying to out-engineer NVIDIA, AMD, Apple, Qualcomm or Intel would be a financial and technical trap. The scale of modern chip development is enormous. The manufacturing, driver work, developer support and software ecosystem required to compete at that level are far beyond any realistic Amiga revival.

The smarter move is to embrace the modern hardware world, not fight it. Use modern CPUs and modern GPUs. Use open standards where possible. Use existing acceleration, drivers and hardware platforms as raw material. Then build the Amiga difference above them: low latency, creative focus, elegant system behaviour, privacy and a sense of user ownership.

The future owner must choose

The hardest job for a future Amiga owner would not be designing a logo or selling a retro keyboard. It would be making choices that some fans dislike.

A future Amiga owner would have to make choices that are honest rather than sentimental. Not every old code can be preserved, and not every classic behaviour should define the modern system. Old software should remain accessible, but it should not be allowed to control the future. The new OS should not be written entirely from scratch merely to prove technical purity, especially if a proven foundation such as BSD gives the project a real chance of becoming usable, stable and maintainable.

The old guard should be respected for keeping the Amiga alive, but they should not be treated as the main design target. The future has to be built for people who may not remember Commodore at all, but who can still recognise the value of a computer that feels fast, creative, private and genuinely theirs. That is the discipline the Amiga needs. Not arrogance, not nostalgia, not purity. Discipline.

A realistic strategy would have three layers. First, a legally clean preservation layer for classic software and games. Second, a modern creative environment that expresses the Amiga spirit without being trapped by old limitations. Third, a developer platform with clear tools, a realistic hardware target, a BSD/Unix-based foundation and a privacy-first operating system that treats the user as the owner. That would let the past remain available while allowing the future to breathe.

Time to move on, but not to forget

The phrase time to move on can sound harsh in a community built around memory. But moving on does not mean deleting history. It means putting history in the right place.

Classic Amiga programs should be preserved and made easy to use. Original machines should be documented, repaired and celebrated. The design achievements of the Amiga should be taught as part of computing history. But the next Amiga, if there is ever to be one, cannot be a prisoner of that achievement.

The Mac survived because Apple accepted, again and again, that yesterday’s Mac could not be allowed to block tomorrow’s Mac. The company abandoned parts of its own past, but usually preserved enough meaning for users to feel that the Mac itself had not disappeared. That is the balance: break the machinery, preserve the meaning.

For the Amiga, this may be the only serious path left. Keep the memory. Keep the culture. Keep the creative spark. But stop pretending that old software, old custom-chip mythology, operating-system purity and old community expectations can carry the weight of a modern platform.

A serious Amiga revival would not ask the world to return to the past. It would take the best of that past, build a bridge from it, use the power of the present, stand on a proven technical foundation, reject the worst habits of data-hungry platforms, and aim at a generation that still deserves a computer with personality, privacy and purpose.