What Is an Operating System?
Series
How Computing Works
βBefore Windows, using a computer meant typing every single instruction in exact text. Get one character wrong and nothing happened β no error message, no suggestion, just silence. Then a mouse arrived and changed everything.β
In 1983, a computer sat on a desk in an office. It had a screen, a keyboard, and a processor capable of doing millions of calculations per second. To use it, you turned it on and waited. After a few seconds, a cursor appeared:
C:\>
That was it. No icons. No menus. No mouse. The computer was waiting for you to tell it exactly what to do, in exact syntax, with no hints. If you typed dir, it showed you a list of files. If you typed DIR, it did the same. If you typed diir or dor or anything else, it replied Bad command or file name and waited for you to try again.
This was MS-DOS. For most of a decade, it was how the world used personal computers.
Why Computers Need an Operating System
Under the casing of any computer is hardware: a CPU (the processor that does calculations), RAM (temporary memory, like a desk where active work sits), storage (a hard drive or SSD, like a filing cabinet), and various chips for handling graphics, sound, networking, and input.
These components are made by hundreds of different manufacturers in thousands of different configurations. Your application β a game, a browser, a document editor β cannot possibly know how to talk to every combination. A game that played sound would need to know the exact technical specifications of your particular sound chip, the exact commands it accepts, the exact memory addresses it uses.
This would be a nightmare. Every developer would have to write code for every possible hardware combination β millions of versions of every program.
The operating system solves this by acting as a universal layer in between. Hardware manufacturers write drivers β small programs that tell the OS how to speak to their hardware. The OS presents a standard interface upward to applications: "If you want to play sound, tell me. I'll handle the hardware." The game doesn't need to know what sound card you have. It just asks the OS.
This division β hardware β OS β applications β is the fundamental architecture of every computing device you've ever used.
The Command Line Era
MS-DOS (Microsoft Disk Operating System) launched in 1981, and for most of the 1980s it ran on the majority of personal computers worldwide. IBM put it on their new PC, Microsoft licensed it, and an entire industry grew around it.
Using DOS required memorising commands. DIR listed files. CD changed directory. COPY copied files. DEL deleted them. There was no visual feedback beyond text output. There was no undo.
The terminal simulation above is a faithful reproduction. Try navigating to C:\GAMES, listing its contents, then going deeper into the DOOM directory. Feel the difference from double-clicking a folder icon. Now imagine spending your working day like this.
DOS wasn't designed to be unfriendly. It was designed for engineers who'd memorised the command set. For that audience, it was efficient β no mouse movement required, no clicking through menus. But for anyone outside that group, computers remained intimidating, specialised tools.
The Graphical Revolution
In the early 1970s, researchers at Xerox PARC β a legendary research centre in California β invented something different: a screen with windows, icons, and a pointing device called a mouse. You clicked on pictures of objects to interact with them. Folders looked like folders. Documents looked like pages. The computer showed you a desk β a desktop.
Xerox mostly didn't commercialise this. In 1979, Steve Jobs visited Xerox PARC, saw what they had, and went back to Apple to build it into a product. The Apple Lisa (1983) and then the Macintosh (1984) brought the graphical interface to consumers.
Microsoft noticed. In 1985 they released Windows 1.0 β a graphical layer that ran on top of MS-DOS. It was clunky and slow. Windows 3.0 (1990) was genuinely usable and sold 10 million copies in two years. Windows 95 made the Start Menu, taskbar, and modern icon conventions standard. By the mid-1990s, the command line was invisible to most users β buried under the surface, still there, still doing its work, but hidden.
Today, the DOS prompt is still inside Windows. Press the Windows key, type cmd, press Enter. The cursor appears. C:\Users\>. Decades of graphical interfaces, and the original text interface is still there underneath.
One OS, Many Forms
Every device with a processor has an operating system. They've evolved to fit their hardware:
- Windows β Microsoft's desktop OS, runs on most PCs worldwide
- macOS β Apple's desktop OS, runs only on Apple hardware
- Linux β open-source, runs on servers, supercomputers, the ISS, and countless embedded devices; Android is built on it
- Android β Google's mobile OS, built on the Linux kernel, runs on most smartphones
- iOS β Apple's mobile OS, runs on iPhones and iPads
- ChromeOS β Google's lightweight OS for Chromebook laptops
These look very different. Underneath they do the same job: manage hardware, run applications, keep processes from interfering with each other, and provide a consistent interface so developers can write software that works across many devices.
The OS is the reason your USB stick works in any computer, your Bluetooth headphones pair with any phone, and a document you save today can be opened by software written in 2031. Compatibility, through a shared layer: that's what an operating system provides.
Ready to explore?
5 interactive activities waiting in the next tab.
A smartphone in 2026 is thousands of times more powerful than the computers that landed astronauts on the Moon in 1969. But those Apollo computers had a tiny, highly optimised operating system that did exactly what was needed. Modern operating systems are vast and complex. What are the trade-offs between a simple, specialised OS and a general-purpose one that can run millions of different apps? Which approach is right for which situations?
Reflect
Every application you've ever used β every game, every document, every website β relied on an operating system doing invisible work underneath it. The OS is the reason you can plug in a USB stick you've never seen before and your computer figures out what it is. How would software development be different if every developer had to write their own hardware drivers from scratch for every device?