Turbo Pascal’s whole compiler and editor fit below a 2011 Mac’s touch command
James Hague’s byte counts make a narrowly dated comparison that still lands without pretending old software had modern obligations.

Turbo Pascal’s compiler and editor fit in 39,731 bytes. In James Hague’s 2011 comparison, that made the whole development environment smaller than the touch command shipped with OS X Lion. A tool for building programs came in below a tool commonly used to update a file’s timestamp. There’s a little compiler-size envy for the terminal.
Hague’s original post identifies the executable as Turbo Pascal 3.02 and dates the comparison to October 30, 2011. That matters. The touch figure is 44,016 bytes for that specific Mac release, rather than the size of every Unix implementation before or since.
Subtracting the two reported figures gives a 4,285-byte difference. Dividing 39,731 by 44,016 puts the Pascal executable at about 90 percent of that touch binary’s size. The joke survives ordinary arithmetic without turning into a claim that Pascal did the same work faster than a file utility.
The development environment combined editing and compilation in one compact executable. Hague describes an integrated compiler with extensions practical for commercial use and particularly fast builds. Those are his retrospective observations; the post doesn’t provide a controlled benchmark against a modern compiler on equivalent workloads.
Other comparisons in his list widen the grin. A minified jQuery 1.6 file is listed at 90,518 bytes, while an iPhone 4S image on Apple’s site is 190,157 bytes. A photograph can contain several compiler-sized helpings of data. The comparison concerns bytes delivered or stored, however, and an image doesn’t have the same purpose as an executable.
The list is useful precisely when its boundaries stay attached. A historical IDE wasn’t carrying every platform integration, language feature, accessibility behavior and security expectation of a contemporary environment. Smaller doesn’t answer whether a new tool is wasteful; it gives somebody a reason to look at what accounts for the difference.
There is also a distinction between a compact core and the complete experience around it. The quoted number is the executable’s size. It shouldn’t silently become the total space used by documentation, libraries, example programs or somebody’s projects. Disk-space nostalgia gets slippery when the measuring tape changes halfway across the desk.
For someone maintaining a developer tool, the interesting question is what the user gets at each layer of the download. Dependencies can be justified and still be worth measuring. A tiny historical program offers a concrete reference point, without requiring the team to remove useful features just to win an argument with a floppy disk.
The original list remains a snapshot of two eras meeting in a byte counter. To repeat it honestly, the version numbers and the 2011 Mac release have to come along for the ride. Today’s touch binary can have its own appointment with the scales.
The compiler packed light.