The December 2022 issue of IEEE Spectrum is here!

Close bar

The Dawn of Haiku OS

How a volunteer crew brought a crack operating system back

13 min read
Software developers gathered recently in Düsseldorf, Germany, to code and collaborate on Haiku

Software developers gathered recently in Düsseldorf, Germany, to code and collaborate on Haiku, an open-source effort that replicates—and improves on—an old operating system called BeOS.

Photo: Andreas Teichmann

It was the summer of 2001, and computer programmer Michael Phipps had a problem: His favorite operating system, BeOS, was about to go extinct. Having an emotional attachment to a piece of software may strike you as odd, but to Phipps and many others (including me), BeOS deserved it. It ran amazingly fast on the hardware of its day; it had a clean, intuitive user interface; and it offered a rich, fun, and modern programming environment. In short, we found it vastly superior to every other computer operating system available. But the company that had created BeOS couldn't cut it in the marketplace, and its assets, including BeOS, were being sold to a competitor.

Worried that under a new owner BeOS would die a slow, unsupported death, Phipps did the only logical thing he could think of: He decided to re-create BeOS completely from scratch, but as open-source code. An open-source system, he reasoned, isn't owned by any one company or person, and so it can't disappear just because a business goes belly-up or key developers leave.

Keep reading...Show less

This article is for IEEE members only. Join IEEE to access our full archive.

Join the world’s largest professional organization devoted to engineering and applied sciences and get access to all of Spectrum’s articles, podcasts, and special reports. Learn more →

If you're already an IEEE member, please sign in to continue reading.

Membership includes:

  • Get unlimited access to IEEE Spectrum content
  • Follow your favorite topics to create a personalized feed of IEEE Spectrum content
  • Save Spectrum articles to read later
  • Network with other technology professionals
  • Establish a professional profile
  • Create a group to share and collaborate on projects
  • Discover IEEE events and activities
  • Join and participate in discussions

Paying Tribute to Computer Science Pioneer Frederick Brooks, Jr.

He helped develop the IBM System/360 and its operating system

3 min read
portrait of an elderly man in a a red tie and blazer with a bookcase in the background
University of North Carolina

Frederick P. Brooks Jr., a prolific computer scientist and longtime professor of computer science, died on 17 November at the age of 91.

While working as a project manager at IBM in the 1960s, the IEEE Life Fellow led the development of the System/360 computer family. It was the first vertically compatible family of mainframe computers. Brooks also developed IBM’s OS/360, the world’s largest software project at the time. He is credited with coining the term computer architecture, which is used to describe how hardware and software are organized to make up a computer system and the operations which guide its function. He wrote The Mythical Man-Month, a book of essays published in 1975 that detailed lessons he learned from challenges he faced while developing the OS/360.

Keep Reading ↓Show less

Learn How Global Configuration Management and IBM CLM Work Together

In this presentation we will build the case for component-based requirements management

2 min read

This is a sponsored article brought to you by 321 Gang.

To fully support Requirements Management (RM) best practices, a tool needs to support traceability, versioning, reuse, and Product Line Engineering (PLE). This is especially true when designing large complex systems or systems that follow standards and regulations. Most modern requirement tools do a decent job of capturing requirements and related metadata. Some tools also support rudimentary mechanisms for baselining and traceability capabilities (“linking” requirements). The earlier versions of IBM DOORS Next supported a rich configurable traceability and even a rudimentary form of reuse. DOORS Next became a complete solution for managing requirements a few years ago when IBM invented and implemented Global Configuration Management (GCM) as part of its Engineering Lifecycle Management (ELM, formerly known as Collaborative Lifecycle Management or simply CLM) suite of integrated tools. On the surface, it seems that GCM just provides versioning capability, but it is so much more than that. GCM arms product/system development organizations with support for advanced requirement reuse, traceability that supports versioning, release management and variant management. It is also possible to manage collections of related Application Lifecycle Management (ALM) and Systems Engineering artifacts in a single configuration.

Keep Reading ↓Show less