What "Running a Program" Means
An app sitting on your computer is, until you open it, just a file doing nothing at all — a block of instructions resting on storage. "Running" it is the moment those instructions are copied into memory and the CPU starts following them.
This is one of those distinctions that sounds trivial and turns out to be everywhere. The gap between a program at rest and a program running is the difference between a recipe and a meal — and it's the seed of the next chapter's big idea, the process.
A Program at Rest
Every app you've installed lives as one or more files on storage — the permanent shelf from the last topic. In that state it does absolutely nothing. It uses no CPU, takes up no memory, and could sit there untouched for years. It's potential, not action: a set of instructions waiting for someone to follow them.
Opening: Loading into Memory
When you double-click an app, the operating system finds its file on storage and copies it into memory, the fast workspace. That copying is exactly what "loading" means — and it's why a big app takes a moment to open: there's simply more to move from slow storage into fast memory before anything can happen.
Notice that the file itself doesn't move. Loading makes a working copy in memory; the original stays on storage, unchanged. That's why you can open the same app again tomorrow, and the day after — the resting copy is always still right where it was.
Running: the CPU Takes Over
Once the instructions are in memory, the CPU begins following them, one tiny step at a time — the work from the last topic. This is the program actually running: responding to your clicks, updating the screen, doing whatever it was built to do. While it runs, it holds a slice of memory for itself and takes turns on the CPU alongside everything else.
Closing: Back to Rest
When you close the app, its working copy is cleared out of memory, freeing that space for something else, and the CPU stops giving it turns. But the app's files on storage are untouched — closing a program removes the running copy, never the program itself. Open it again and the whole cycle repeats from the beginning.
A cookbook makes the rhythm obvious. The book on the shelf is a program at rest: full of instructions, doing nothing. Cooking a recipe is running it — you carry the book to the kitchen (load it into memory), then actually follow the steps (the CPU runs them). When you're done you put the book back, unchanged. The meal is gone, but the recipe sits exactly where it was, ready to cook again.
- "An app I installed is always running." Installed only means its files are on storage. It does nothing until you open it and it's loaded into memory.
- "Running an app changes the app itself." Running works on a copy in memory; the program's files on storage stay exactly the same.
- "If an app isn't on screen, it isn't using memory." Minimized and background apps are still running — still holding memory and taking CPU turns — even when you can't see them.
- "Closing an app deletes it." Closing clears the running copy from memory; the app's files stay on storage, ready to open again.
- "A running program" is exactly the idea the next chapter names a process — one of the most-used words in all of computing.
- Later in this course, a container is described as essentially an isolated running program; this is the picture that makes that idea click.
- It explains why closing apps speeds up a sluggish computer — the memory they held is reclaimed for what you're actually using.
- It's why "is it installed?" and "is it running?" are two different questions, and keeping them separate saves a lot of confusion later.
Knowledge Check
What does it actually mean to "run" a program?
- Its instructions are copied into memory, and the CPU starts following them
- Its file on storage is permanently changed into a running version of itself
- A fresh copy is downloaded from the internet each time so it stays current
- The CPU reads the instructions straight from storage, never using memory
You installed an app last week but haven't opened it. What is it doing right now?
- Nothing — it's just files resting on storage until you open it
- Running quietly in memory and using a little of the CPU in the background
- Slowly loading itself into memory so it's ready the moment you click
- Checking for updates on the CPU, which is why installed apps slow things down
When you close a program, what happens to it?
- Its running copy is cleared from memory, but its files stay on storage
- Its files are deleted from storage, which is how closing frees disk space
- It keeps running in memory until the computer is fully shut down later
- It's moved from memory onto storage, changing the original program file
You got correct