AmiBrowser: the Chromium engine running on a Linux host talking to a 68K Amiga application running inside a 68K emulator

We removed ads from OSNews. Donate to our fundraiser to ensure our future!

Covering the Amiga world is always a bit of a crapshoot, since for what is surely an incredibly small segment of the computing world, it happens to be incredibly complex, with multiple competing Amiga-ish operating systems and hardware platforms, all worsened by many empty promises and bitter animosity flying every which way. This makes it hard for an outsider to get a firm grasp on what’s going on, but as always, I’ll try my best.

The news here is that AmiKit has released a new browser for the classic 68k Amiga that can load modern websites. The browser is called AmiBrowser.

AmiBrowser is an HTML 5 capable web browser built for 68K with Zune/MUI. Ituses ARM libraries to power the native rendering of the web pages.
↫ AmiKit press release

AmiBrowser is exclusive to AmiKit’s own Amiga-like hardware, the A600 GS and A1200 NG, both of which are replacement boards for the original Amiga 600 and 1200, respectively. How do these machines work? Well, they come in the shape of their original counterparts, but with far fewer chips, and one crucial addition: a little Orange Pi Zero 3 (in the case of the A1200 NG, at least) daughterboard that contains the actual ARM SoC that powers the machine.

The way this setup works is that the Orange Pi Zero 3 boots into a minimal Linux environment with a launcher-like interface, which can in turn load up the Amiberry classic 68K Amiga emulator that can communicate with its ARM Linux host. It’s inside this 68K emulator where the actual operating system runs. This Amiga-like operating system is called AmiBench, which is, very simply put, a modified variant of the 68K version of AROS, combined with libraries and components that can make use of the ARM processor.

And so we finally arrive at this new browser. This new browser runs the Chromium Embedded Framework in the host Linux environment on the ARM processor, forwarding its rendering towards a native 68K Amiga/AROS application that’s running inside the 68K emulator. In between the CEF running on the Linux host and the native Amiga 68K application running inside the emulator sits a glue layer that takes care of the communication between the two sides. It’s an interesting approach to a very difficult problem: how do you run a modern browser on a hardware platform – 68K, in this case – that is horribly outdated and far too slow to deal with modern websites?

It’s an interesting approach, but it also feels a little bit like a house of cards. That being said, if the choice is between no access to the modern web and shaky access to the modern web, I’d still choose the latter.