Amiga and the revolution yet to come

I had some musings on the Amiga interface. I promise I’m not trying to start a flamewar, but I’m honestly puzzled about this OS and how the interface was supposed to carry this hardware to greatness.

(I post it here because I know folks won’t let this descend into petty squabbling.)

1 Like

Well, it was a WIMP at reasonable cost at a time when there weren’t many of those.

But for me, the advantage of the Amiga was not in the GUI but in the OS: it seems nicely constructed, in terms of facilities and libraries. Not just the multitasking, but the interprocess communication, the runtime loading of libraries, the official interface to claiming and releasing resources, the hierarchical filesystem. The machine wasn’t too bad to program, it was affordable, it had pretty good performance for the time, there was a C compiler at reasonable cost, the graphics and sound facilities were impressive.


Thank you. These are awesome points.

I’m curious if you had a chance to look at Atari’s TOS and GEM. I’ve been looking at it and it seems to have some interesting construction (though I think most of the good bits came out of Atari’s efforts). I know it doesn’t have multitasking, but I’m finding that VDI is an interesting beast, albeit a bit slow.

Also, how much was a C compiler for the Amiga? I know the Atari development package was $300 fir the documentation and Alcyon (which was serviceable, but not great) but I’ve never been able to find a price on the Amiga development tools / kits.

I hear what you’re saying. My best friend in college had an Amiga 500 and worked at ASDG. He wrote some amazing things and I could see that there was a lot of intrinsic goodness about the Amiga, but as someone who is more design focused, I had a hard time seeing past the atrocious UI. It’s a shame because it seems that they could have easily fixed this issue even by just hiring one artistically minded person. I suspect that many others had the same impression as you and I - it shows the importance of design.

1 Like

Ah, there you have my weakness: I don’t have familiarity with GEM or TOS. I have, very very briefly, run GEM on the BBC Micro (with an (emulated) x86 second processor) but never tried to do anything with it, still less to program it.

1 Like

I was a long time Amiga user. I think what you’re missing is that the Amiga had all this stuff in 1985. Here are some of the things the Amiga gave:

  1. Plug-and-play. This is something boring today, but back then? You could just plug in an expansion card or drive or whatever and it just worked.
  2. Multi-tasking, which was really awesome for a whole ton of things rather than saving/quitting/opening another program and so on.
  3. Common file formats. The IFF format meant that you could create/save an image file with one program and do more work with it with another program. Remember, this was an era where it was common for you to only be able to open a file with the program that created it. Ugh!
  4. Multiple screens. On the Mac, Atari ST, and other GUIs, you didn’t have multiple screens. The Amiga let you have multiple screens - as many as you could fit in video RAM, each with its own resolution, bit depth, and palette if you wanted. Admittedly, this is a capability that only really shines if you also have multi-tasking, but it was sure awesome. You could even view multiple screens at a time, working like multiple windows separated vertically.

Factors 2-4 had a big synergistic effect. The Amiga was the first computer where you had this ability to set up a workflow of creating/rendering with one program, and then editing the output in another, compositing stuff, doing textures or whatever, and coding in another screen … you could modify what you needed and test. It was just so radically different and superior to working on single tasking computers.

That said, the overall look and feel was not consistent. Where Apple set guidelines on what the look-and-feel should be for applications, Commodore just threw out a toolset and let developers make their applications however they wanted. On balance, this was a good decision because it gave developers freedom to develop novel interfaces suitable for their applications.

The reason why most Amiga games booted directly into the game was because most users had a stock Amiga 500 with only 512k of RAM. Workbench consumed some of that RAM. But there were also a lot of games which could run from Workbench, and this was a nice thing for those of us with expanded Amigas with hard drives and such.

But the Amiga was able to do all this with extreme efficiency compared to other computers - even single tasking computers. It was really efficient with RAM, so an Amiga could cost a small fraction of a Mac or PC clone and offer better performance. (The custom chips helped a bit, but not really by the time we were getting into 68030s and such.) An Amiga with 1MB could do a lot of multi-tasking applications, whereas a *nix machine wouldn’t even work at all without at least 3MB.

Anyway, there’s very little that the Amiga has to offer that modern computing with Linux lacks. There’s not really any benefit to saving a slight amount of video RAM with mixed resolution and color depth. Who cares? The RAM efficiency is … yawn. We’re long past the days of caring about MEGAbytes of RAM. Multiple workspaces is a better paradigm than multiple screens. So whatever … there is no Amiga revolution awaiting us. It was an amazing computer for its time. But we have better stuff now.


I don’t remember how much I paid for Manx Aztec C compiler (one of the two popular C compilers for the Amiga, at least here in the USA). I think it was around $150. Anything close to $300 would have been way out of my league.

As with their 8-bit computers, Commodore was very open with Amiga documentation. You could get all the documentation you needed pretty cheap with the official Programmers Manual, but man it was a lot more complex than the 8-bit Programmers Manuals.

I also used Atari STs, but not nearly as much. I actually used Atari STs before Amiga. As a simple launcher for (single tasking) applications, it was fine. I liked the fact that it booted up fast due to being in ROM. But other than that, it was nothing remarkable.

1 Like

Oh, another thing that was really sweet about the Amiga OS - sensible ramdisk. Like modern tmpfs, the Amiga had a ramdisk that dynamically took up as much or as little space as needed. (Contrast with fixed size ramdisks, which are … a pain.) Tmpfs is nice on modern Linux, but an absolute game changer on stock floppy Amigas.

Think about it. You only have one floppy drive, but you want to work on stuff which requires multiple discs. Maybe you want to store working files on the ram disk while swapping application floppies. Maybe you want to store some executables on the ram disk so you don’t need to swap discs. With a flexible ram disk, you can do this.

It’s also great even if you have a hard drive. A hard drive is pretty slow, but you can copy your heavily used executables on your ram disk … it is FAST! And this applies to stuff you’re working on in general. Remember, this is way before fast SSDs. If you had 3MB of RAM? Oh, you could really sizzle.

1 Like

I bought a half-share in Matt Dillon’s DICE, which can be found online here (described as a generally useful small 68k compiler) (1995 review here). I think it was £30 or thereabouts, although I see now it’s described as shareware. (I also see the review says it’s £130.)