When a Gigabyte Was a Capital Expense
In 1980, a gigabyte of storage could cost about half a million dollars. That figure makes code efficiency easier to understand as an economic constraint, not just a programmer’s preference: every extra byte had to fit on scarce, costly storage—and often in even more limited working memory while a program ran.
A gigabyte is a billion bytes, but software of the era was commonly built within budgets measured in far smaller units. Developers had reason to conserve space: they could use compact data formats, avoid storing duplicates, and spend time trimming programs to fit available hardware. Those choices could make software harder to build or maintain, but wasting storage was expensive.
The Tradeoff Shifted
As storage became cheaper and more plentiful, the balance changed. Teams could accept larger files in exchange for richer graphics, audio, and other features, or because using more space saved development time. The cost of a programmer’s effort did not fall in step with the price of a disk, so optimizing every byte became less compelling in many projects.
That does not mean modern software has no reason to be efficient. Large downloads still consume time and bandwidth, and games compete for space on devices. But a 50-gigabyte download now feels ordinary in a way that would once have been financially extraordinary: at the 1980 price per gigabyte, that much storage would correspond to roughly $25 million. The comparison captures the scale of the shift—not what a game download would literally cost today, but how dramatically the economics of storing digital information changed.
