The Computer
How does a machine go from a powered-on board to something that browses, plays music, and works for you? In this chapter we take one apart, starting from the moment you press the power button.
What's inside
Here's a computer you use every day. Let's slowly lift the case off — don't worry, nothing breaks in here.
With the shell gone, a mainboard appears. The actual workers are just a handful of parts: the CPU, memory, the disk, and a network card. Each does exactly one job.
Give each one an identity: the CPU is the brain — it thinks. Memory is the workbench — things you're using right now. The disk is the filing cabinet — things stored away. The network card is the door to the outside.
And the motherboard is the desk that lets them pass things to each other. Together, that's enough to stream video and write documents. Hover over each part to meet it.
From black screen to desktop
The instant you press power, current sweeps across the board — item one on the machine's wake-up checklist: confirm I'm alive.
Firmware checks and initializes essential hardware. Older machines often use BIOS; modern ones usually use UEFI. This checklist is an illustration.
Firmware finds a bootloader, which loads the operating system. The whole operating system isn't stored inside a tiny boot sector.
The OS is loaded into memory and takes over. The desktop lights up. Every boot, same routine — from zero volts to desktop.
The butler you never see
The desktop looks quiet now. But take an X-ray, and you'll find the operating system constantly busy — juggling three jobs at once.
Job one: files. Where your photos and documents live, which folder holds what — it keeps the books.
Job two: programs. Who runs, how much memory each one gets, who goes first. Each running program is what insiders call a “process”.
Job three: hardware. Every keystroke, every mouse move, every packet the network card receives — it relays them all. Without it, you'd be staring at a glowing slab.
What happens after a double-click
There's a browser icon on the desktop. Double-click it — behind that gesture is a whole assembly line.
The OS finds the program on disk and makes the needed code and data available in memory. Real systems can load pages on demand rather than copying the entire program at once.
Then the CPU executes its instructions one by one — drag the slider below to slow the process down and watch.
The moment the window grows out of the icon, the program is alive. The disk stored it, memory holds it, the CPU runs it — the three roles complete their first relay.
Why it lags, and why restarting works
Four programs are open now: browser, music, chat, video editing. They look simultaneous.
This diagram shows one execution resource sharing time between programs. Modern multi-core CPUs can also run tasks in parallel; time-sharing and parallelism coexist.
But memory is finite. Every open program claims a piece of the workbench. Try the slider below — open a few more.
Memory pressure can trigger data swapping and slow things down. Storage, networks, and application bugs can also cause lag. Restarting clears temporary state, but the system still uses memory and the underlying cause may remain.
You can now read a computer
It's a set of parts each doing one job, an operating system playing butler, and programs doing the actual errands. You can already explain your friend's “my computer is so slow” — for real.
But what exactly is a program? Who writes it, and with what? Next chapter, we take “program” apart.