Today in Tedium: Operating systems are the cockroaches of the digital revolution. They’re everywhere, hiding in low-level crevices, and most of the time, you don’t really notice when they’re there—except, of course, when they draw attention to themselves. (Cough, cough Windows 8 cough.) But most of those operating systems fade from view—except when they don’t. Case in point: The company Arca Noae claims it’s about to launch a brand-new version of IBM’s coulda-been ’90s contender, OS/2. Apparently, there are people who still use it! Tonight’s Tedium surveys the landscape of obscure operating systems and highlights the ones that are with us in ways large and small. — Ernie @ Tedium
“We’re specifically dedicated to maintaining OS/2 and derivative operating systems as long as possible. As long as there’s hardware that will support OS/2, that’s what our focus is.”
— Lewis Rosenthal, one of the co-founders of Arca Noae, during a talk at the 2015 Warpstock Europe conference, discussing the firm’s plans to manage and offer support to still-existing OS/2 users. (The company is one of a couple of this nature, actually; eComStation supports a number of Fortune 500 companies still using OS/2.) Arca Noae is also working to solve a more practical problem, according to TechRepublic: The fundamentals of OS/2 have largely held up since the ’90s, but installing it is a pain in the butt because the IBM versions of the operating system absolutely require a floppy drive, and the system doesn’t actually work on modern hardware because the operating system doesn’t support UEFI. (Not to be lost here: Yes, OS/2 has enough of an existing fan base to support conventions! In fact, Warpstock is held both in the U.S. and Europe every year, with the European edition taking place next month.)
Five operating systems still carrying the vintage torch as of 2017
- BeOS was supposed to be former Apple executive Jean-Louis Gassée’s big mark on the world; instead, it faded from view. (Gassée’s legacy might actually be found in his excellent commentaries on the blog Monday Note.) While BeOS hasn’t been developed since August of 2000, it has found a successor in the form of Haiku OS, an open-source project being maintained by a group of volunteers.
- “Any program that works on MS-DOS should also run on FreeDOS,” the website for the FreeDOS project claims, and it’s certainly yeoman’s work to keep an open-source variation on DOS alive—with games, old word processors, and embedded systems the primary use cases. At Network World back in February, Bryan Lunduke of SUSE wrote a very gushy take on the DOS-based platform, which he notes has been in active development for longer than MS-DOS actually was.
- “Remember that Amiga OS 4.0 is only a temporary step to Amiga OS 5.0,” the user group website Convergence International boldly claimed in 1998. The die-hard enthusiast platform Amiga OS is still with us, but 19 years later, it hasn’t passed version 4.1, though it remains relatively up to date. (It is the subject of a great documentary, however.)
- WebOS shoulda been a contender. Built by Palm from the ground up as a replacement for its dated Palm OS, webOS was a sheer beauty at the time of its 2009 launch. Less than two years later, it was basically dead in the water at Hewlett Packard … until LG bought the technology and started using it for its smart TVs for some reason.
- The Commodore 64, which drops users into a version of BASIC as its operating system, isn’t currently seeing active development or anything like that, but that doesn’t mean it isn’t in active use. Last year, Commodore USA’s Facebook page reported that an auto repair shop in Gdansk, Poland was still running its business on a C64—which Geek.com put into sharp relief in the wake of then-recent comments by Apple executive Phil Schiller about people using 5-year-old computers.
The greatest operating system you’ve probably never heard of unless you know what a Unisys ICON is
Two years before Research in Motion was born in Waterloo, Ontario, Canada, another Canadian firm was putting the into action an idea that would eventually prove a key part of the modern-day BlackBerry’s entire business. Not that they knew it at the time.
Quantum Software Systems, as it was first called, came about after two University of Waterloo students, inspired by the real-time programming lessons they were learning in their computer science class, decided to create a similar real-time system for the relatively-new IBM PC. One interesting element of the platform they created, first called Qunix and later renamed QNX, was that it was designed around a microkernel architecture, a somewhat unusual move at the time.
See, most operating systems are built around the idea that the kernel, or central nervous system of the OS, manages a number of basic tasks that every application needs, a model described as “monolithic kernel.” On the other hand, microkernels are designed to offload just about everything, treating every element of the system’s operation as an optional part of what makes it work. This approach has been controversial at times: In 1992, MINIX author Andrew S. Tanenbaum (whose operating system, released a few years after QNX, also relied on microkernel) got into a large-scale Usenet flame war with Linux creator Linus Torvalds over the differences between the two approaches. (Short version: Microkernels are way more stable; monokernels are better for performance.) The debate, among other things, helped forge Torvalds’ reputation as a hot-head.
Whatever the case, QNX was a head-turner upon its release. In PC Magazine, computer consultant James B. Morris compared the operating system to “a juggler who keeps a lot of balls in the air.” The next year in the same magazine, columnist Kaare Christian wrote with surprise about the the operating system’s strong functionality despite the small size.
“The extremely compact programs make it possible to place QNX’s 50 utilities on a single floppy disk and make it possible for the QNX system to work on a machine with 128k and floppies,” Christian wrote. “Thus, QNX can fill more programs in memory at once.”
The operating system has remained active ever since, though never went mainstream among home computer users, mostly sticking to embedded and industrial needs. That is, minus a short period in which the Ontario government had a really good idea.
In 1983, the government funded work on a homegrown PC for schools. The Unisys ICON workstation, as it was called, was effectively created as a way to standardize the use of computers in the province’s schools.
The operating system on the machines? QNX. It would never get this close to mainstream home computing ever again.
It was really another mainstream device—one outside the home—where it quietly won everyone over.
How BlackBerry’s fortunes are slowly being turned around by a 35-year-old operating system
In 2010, Research in Motion was on the ropes.
The problem, simply, was that it made a bad bet about the role that smartphones were going to play in modern society. They were successful for a while, but the company treated them as sort of a general commodity device that would be handed out to employees by businesses—an approach that held up, at least until Apple released the first iPhone and hinted that everyone might someday want one.
Already losing steam and suddenly competing in the tablet space as well, RIM found itself in a position where it had to quickly catch up with Apple and Google. But its operating system wasn’t up to snuff. It grabbed something, anything, to help it catch up against its new competition—and that turned out to be QNX, a company that by this point had started to embed itself as the nervous system used by many cars.
Cars are the perfect use case for something like QNX. When it comes down to it, you don’t care about your in-dash entertainment system being fast while you’re driving—you simply want to ensure that, when you change the station, it simply works. (And QNX, of course, was so well-used at this point that it was bulletproof—hell, the space shuttle uses it.)
This approach certainly sounded appealing when applied to a tablet or a mobile device, and while the reviews were somewhat mixed for the ensuing PlayBook (which, weirdly, initially required a separate BlackBerry device for use of features like email and messaging), the OS received nice notices.
“As an outsider looking in, it almost feels as if RIM has been able to do as much in six months working on QNX for the PlayBook as they have in the past six years working on the old BlackBerry OS for their phones,” wrote “CrackBerry” Kevin Michaluk.
And it makes sense. In a lot of ways, it was not the same QNX as was first shown off in the ’80s. While maintaining its general approach, the operating system was continually updated for shifting industry needs, and by 2010, it had become the standard-bearer for many embedded systems. (But not all, of course; OS/2, famously, still gets used in ATMs and checkouts, which is why they still hold conventions for it.)
As we all know, QNX did not save the BlackBerry phone. But it might help save BlackBerry the company—a firm that has been the recipient of more free business advice than perhaps any other in the world. The turning point came in 2014, when Ford decided to drop its contract with Microsoft in favor of QNX, which (combined with other deals) had the effect of making the operating system something of a de facto standard for cars with onboard infotainment systems.
Soon, the hits kept coming: Apple, seeing a market it wanted into, built its CarPlay system on top of QNX (with BlackBerry’s blessing). And John Chen, the turnaround artist who has masterminded BlackBerry’s return to prominence, noted the sheer excitement companies had about QNX in a 2014 earnings call:
QNX is probably one of the crown jewels. Every time I come here, our partners call me and customers call me that really want to work with us on QNX...The plan is to invest in this and grow. The plan is to go by other vertical because we are doing very well in automotive vertical, we are going to continue to focus on that, but we’re going to start looking in adjacent verticals to expand the business. In addition to that, we’re going to build a platform that are cloud based, that is going to be machine-to-machine based architecture.
That seemed like a somewhat weird thing to say in early 2014, but the Ford deal strengthened the case, while the push toward self-driving cars suddenly made automobile operating systems an interesting field. More notably, the company is profitable again for the first time in a while.
Apple appears to be taking close notes—despite being a California company, the iPhone giant apparently is building its self-driving car operations out of Ottawa … basically to look over BlackBerry’s shoulder.
Fortunately this time, BlackBerry has a bit of a head start.
The number of years that ReactOS has been in development. The operating system, which aims to completely recreate vintage Windows software, is an impressive feat, though with a tiny team compared to the giant offices full of developers Microsoft threw at those old versions of Windows, it’s unlikely that the operating system will ever reach parity with even vintage versions of Windows. Currently, it works akin to, say, Windows Server 2003. That said, its Twitter page is worth watching as the operating system slowly gains the ability to run different apps.
The thing that’s really interesting about many of these operating systems is that they persist, right under our noses, in ways big and small.
Even though our desktops are generally running macOS, Windows, or a flavor of Linux, there are people that still care about operating systems we’ve never heard of, nor have ever given a second look.
Whether it’s driven by a community of enthusiasts, a specialized use case, or a need for security, there will always be operating systems that fall outside of mainstream release cycles.
In an era when light bulbs running an embedded operating system are seen as a legitimate threat, perhaps the best form of security is simply using a platform that’s useless to basically everyone but you.
Sometimes, obscurity is a good thing.
Clarification: An earlier version of this article initially didn’t specify why a BlackBerry phone was often necessary for use with a PlayBook. This was due to a software issue with the initial version of the device that was eventually resolved.