7/23/2026 at 9:03:12 AM
For some aspects, the Amiga is still ahead of today's tech. AmigaOS 2.x layed out a vision of the desktop UI as a malleable and personalizable toolbox (or one might say "workbench" heh) like no other operating system since then.The Amiga team envisioned a desktop environment future which focused on being a productivity tool instead of an interface for passive media consumption and doom scrolling, where graphical user interface and command line environments were tightly integrated with each other, where the philosophy of 'doing one thing right' was extended to the GUI and where highlevel operating system features could be extended via a standardized plugin architecture. The closest thing we have today is probably game modding.
This grand idea was essentially "sacrificed on the altar of commerce" on Windows and macOS. Desktop Linux could carry that flag forward if it had a consistent vision for the desktop environment, but alas it wastes those resources on irrelevant technical details like creating yet another half-assed Wayland compositor and that way increasing fragmentation instead of reducing it.
As a former Amiga user it amuses me to no end that we're now pivoting back to TUIs (see Claude Code) instead of attempting again to make those two worlds (GUI and cmdline) work together.
by flohofwoe
7/23/2026 at 10:52:04 AM
It isn't as if the tools aren't there, Powershell with .NET/COM (yes COM really needs a DX improvement), AppleTalk/XPC/zsh, GNOME/KDE/D-BUS.Yet as you very well point out, it is a mess, and no where close to using AREXX or Datatype libraries.
by pjmlp
7/23/2026 at 3:02:55 PM
It's so sad to see what happened to AppleScript/the Open Scripting Architecture.When it arrived you could basically build your whole app around it as a message-passing/object system and get automatic, deep scripting integration.
NeXTpple never properly integrated it into Cocoa, and eventually they wanted a more user-friendly GUI scripting system and put their NIH syndrome to work and made Automator, which never took off because it was too simple. They they built Shortcuts off an acquihire and now Shortcuts introduces NSUserActivity as the new way to... build your whole app around a message-passing/object system and get automatic, deep scripting integration. Except now we have all this weird magic templating going on.
by kalleboo
7/23/2026 at 11:58:07 AM
BeOS/Haiku uses datatypes nativelyby smallstepforman
7/23/2026 at 12:08:03 PM
Interesting, I didn't use it much beyond the famous demo CD.by pjmlp
7/23/2026 at 2:12:11 PM
There is https://en.wikipedia.org/wiki/AROS_Research_Operating_System nowadays.It lacks a usable browser for todays websites. Maybe someone gets into the vibe of agentically coding one.
While being at it, the foundations could use heavy fuzzing, lift them up to Open/NetBSD at least. A few looks into Genode for technical inspiration wouldn't be wrong, maybe a port of Aros atop seL4/Genode could be supreme. Same as Haiku.
by LargoLasskhyfv
7/23/2026 at 1:00:59 PM
> AmigaOS 2.x layed out a vision of the desktop UI as a malleable and personalizable toolbox (or one might say "workbench" heh) like no other operating system since thenCan you say more? I had (and loved) an A1200 and appreciated what things like ARexx could do, but I don't know what you're alluding to here that things like the Mac didn't ultimately implement as well (though sometimes less well; I miss multiple screens to this day)
by marbletiles
7/23/2026 at 2:06:10 PM
Back on the Amiga 3000 we had built our asset creation tools for a game that eventually ended up as Urban Assault on the PC. This was a wild mix of custom-made and standard tools wired together via AREXX and controlled with a little macOS dock like icon toolbar, and all integrated with the workbench file manager.E.g. one such custom workflow would be to "pipe" an image file created in DPaint into some standard image processing tool (forgot the name, basically like ImageMagick, but as a UI tool) to change the pixel format, scale and filter, then piping the resulting output image into a custom tool to convert into an engine specific texture format, all the while updating some asset database files, and IIRC also creating an icon file in the process.
Most of this can also be achieved with a pure cmdline workflow today via Python or Node (by glueing together tools like ImageMagick, ffmpeg, various asset pipeline tools), but the special sauce on the Amiga was that most 'modern' UI tools adhered to standards defined by the Amiga team for cmdline usage and scripting.
The 'plugin architecture' was mostly about datatypes (globally available file format encoders/decoders), BOOPSI UI components and 'Commodities' (IIRC small background tools that could intercept and manipulate system events).
by flohofwoe
7/23/2026 at 3:08:43 PM
> most 'modern' UI tools adhered to standards defined by the Amiga team for cmdline usage and scripting.One minor example of the usability was that the ReadArgs() call was fairly extensively used within a year or two after it was introduced and meant that the "?" command line option for help worked "everywhere" and would give a machine parseable, semi-typed options list (annotations like "/T" for toggle, "/N" for number etc.)
by vidarh
7/23/2026 at 3:07:28 PM
Many newspapers in the 90's had their whole classified sections automated using custom AppleScript workflows, it was one of the big things that kept publishers on the Mac instead of Windows, since Microsoft didn't have anything to compete (OLE/VBA was a joke for these things)by kalleboo
7/23/2026 at 3:24:16 PM
Yep the whole AppleScript and (Quark Xpress) Xtension mechanism was remarkably sticky. Apple were treading dangerously during the OSX transition when it became clear much of that would never port over, but Quark was losing their grip by then.MS were trying a huge NT push into the DTP industry that basically hit that wall and aborted.
by mosura
7/23/2026 at 4:41:11 PM
> some standard image processing tool (forgot the name, basically like ImageMagick, but as a UI tool)Possibly Art Department Professional (aka ADPro)?
by LocalH
7/23/2026 at 5:48:24 PM
Hmmm, I use Claude Code to make those two worlds work together -- where a GUI is an obvious complement (visualization, discoverability)by waffletower