From Scratch or Legacy: The Decision Behind New Operating System Designs

When it comes to designing a new operating system, the decision to start from scratch or base it off an existing one is a crucial one. This choice impacts not only the development process but also the feasibility, performance, and scalability of the final product. In this article, we explore the considerations behind this decision, focusing on the examples of Google Fuchsia and custom OS development practices in the industry.

Google Fuchsia: A New Approach

Google Fuchsia, recently gaining attention as a potential replacement for Android, is built from the ground up. Unlike its sibling Android, which is deeply rooted in the Linux kernel and other open-source components, Google Fuchsia is designed to be a microkernel-based operating system. This novel approach is driven by its microkernel Zircon, which is built on the foundations of an embedded kernel called Little Kernel. The project's goal is to avoid the use of any GPL code, making it a unique endeavor in the history of operating systems.

The choice to start from scratch with Google Fuchsia is a significant one. By not relying on existing open-source components, Google aims to create a more secure, efficient, and customizable operating system tailored to its needs. This approach allows for tighter control over security, performance, and resource management, which are critical for a variety of applications, from mobile devices to smart home appliances.

Custom OS Development: The Reality Behind Building From Scratch

Standing at the crossroad of innovation and pragmatism, many companies opt to build their own operating systems, especially when off-the-shelf solutions are not viable. For instance, in the early stages of developing a Linux-based storage device, the option to use an existing, pre-built operating system was never considered. The rationale behind this decision is largely driven by the need for a highly cost-effective and efficient solution. Given that the CPU for such devices is budget-friendly, the time and resources required to design and implement a custom OS from scratch are justified.

The actual process of building a custom OS is complex and fraught with challenges. The development of a customized kernel and a core system, such as a BusyBox distribution, is just the beginning. The real difficulty lies in reliably building the remaining packages and integrating them into the system. This process can be labor-intensive and time-consuming, often requiring adjustments in link and compiler options across hundreds of packages. Moreover, the building system of a custom OS must be robust, capable of handling the vast number of packages required for a full-fledged operating system.

The key to overcoming these challenges lies in the build systems used in popular distributions such as Debian, Ubuntu, Arch, and Centos. These build systems have evolved to handle the complexity of large-scale software projects, making it feasible to manage hundreds of deliverables efficiently. For Windows, the build system is even more intricate, reflecting the need for a highly polished and secure operating system.

Legacy Systems and Modern Challenges

While the benefits of building a custom OS from scratch are clear, many modern operating systems are still based on legacy code. For example, the vast majority of operating systems for TVs, routers, and other embedded devices are based on Linux. This is primarily due to its open-source nature and the extensive ecosystem of tools, libraries, and communities that support it. The ease of use and the availability of resources make Linux an ideal choice for these applications, as it can be tailored to fit specific needs without the need for a complete ground-up redesign.

The principle of "the thing that hath been, it is that which shall be, and that which is done is that which shall be done" (Ecclesiastes 1:9) resonates strongly in the world of operating systems. While innovation and the quest for a fresh start are admirable, the reliability and proven track record of long-standing, well-supported operating systems cannot be overlooked.

Examining the case of Google Fuchsia and the custom OS development practices in the industry, we see that the decision to build from scratch or to leverage existing systems often depends on the specific requirements, resources, and goals of the project. Whether through an innovative approach like Fuchsia or the pragmatic use of a mature and well-supported system like Linux, the choice determines the future of the operating system and its applications in a rapidly evolving technological landscape.