system software vs application software

Software splits into two broad families by who it serves. System software exists to run and support the computer itself — it serves the machine and other programs. Application software exists to do a task a person actually cares about — it serves the user directly. A rough analogy: the wiring, plumbing, and elevator of a building are system software (you do not move in for them, but nothing works without them), while the furniture and the people doing work in the offices are the applications (the reason the building exists at all).

System software includes the operating system and its kernel, but also a supporting cast: device drivers, the linker and loader that prepare programs to run, system libraries, command shells, and utilities like file managers and disk tools. These programs manage hardware, provide common services, and create the platform on which everything else sits. Application software is what you launch on purpose to get something done: a browser, a spreadsheet, a game, a photo editor, a chat app. Applications lean on system software for everything low-level — they ask the OS to open files and draw on screen rather than doing it themselves.

The line can blur, and that is worth admitting. A web browser feels like a pure application, yet it contains a whole runtime that is platform-like. A text editor is an application, but a compiler is usually counted as system software because its job is to build other software. The useful test is the question who is this program primarily for: if it mainly serves the user's goal, it is application software; if it mainly serves the machine or other programs, it is system software.