Software, Data, and the Difference

Think about a music player and a song sitting on the same drive.

You already know these are different sorts of thing. One is an app you open; the other is something you listen to. On storage, though, both are represented as bytes. Names, file formats, and operating-system records help software recognize what each item is for, but neither sequence of bytes acts by itself.

So what makes one of them do the work, and the other get worked on?

Instructions and data

The difference is the role the bytes play.

Software includes programs and the supporting data packaged with them. A program contains instructions for work the computer can carry out; its package can also include icons, button labels, sounds, and default settings. Installing an app puts that package on storage, ready to be loaded when you open it.

Data is the material those instructions read or change: your song, your photos, or the document you are typing right now.

Context decides the role. A Python source file is text data while an editor displays it, then supplies instructions when Python reads it to run the program. The bytes have not changed between those two moments; the program using them and the requested job have.

Installed is not the same as running

Here is where the words we all use every day get sloppy, and it causes real trouble later.

An app sitting on your drive is doing nothing whatsoever. It is a set of instructions, waiting. Double-click it and a chain starts:

1. The computer reads the program’s instructions from the drive.

2. It loads the parts it needs into RAM.

3. The CPU begins carrying those instructions out.

4. The program takes your input, changes data, and puts things on screen.

Now the program is running. Some programs also start automatically or keep background work running after their window closes. Installation means the program is available on storage; an open window is not a reliable test of whether it is running. Chapter 3 will give the operating system’s name for that managed running work.

Programs lean on other programs

One more thing about that music player, and it matters more than it sounds.

It contains no instructions for your particular headphones. None for your brand of drive, and none for drawing a window on your screen. It could not possibly hold all of that, and if it tried, it would break the day you bought new headphones.

So it does not try. It asks. “Open this file.” “Play these samples.” “Give me a window.” Something underneath deals with the specifics.

That something is the next lesson, and it is why a program written years ago still runs on hardware that did not exist when anyone wrote it.