Who did it first, and why should you care?
The phrase is associated with modernist architect Ludwig Mies van der Rohe, who popularized it in the 20th century. But it first showed up in Robert Browning’s 1855 poem Andrea del Sarto: “Well, less is more, Lucrezia.”
This idea applies especially well to software. Fewer abstractions, dependencies, features, and moving parts make systems easier to understand, debug, and maintain. In UI/UX, simple interfaces with a clear hierarchy perform better because users can reason about them quickly. In system design and software architecture, restraint often leads to cleaner boundaries, fewer failure modes, and better long-term design.
Who did it right?
I think UNIX is a good example of this. Its development began at Bell Labs in 1969. It comes with a collection of small utilities that do one thing and do it well. The philosophy (from Doug McIlroy) is that complex tasks can be performed by combining these utilities with pipes.
Even the utilities less and more are examples
of this. They are both used to view text files, but less is more
powerful and flexible than more. Mark Nudelman wrote less in the early
80s because he needed a more that could scroll backwards. The name is a
joke about “backwards more”. On macOS, more is literally less.
less
- Can scroll backwards, even through piped input
- Can search backwards as well as forwards
- Doesn’t quit when it reaches the end of the file
-
Can follow a growing file, like
tail -f(pressF) -
Commands are based on both
moreandvi
From the man page:
Less is a program similar to more(1), but it has many more features. Less does not have to read the entire input file before starting, so with large input files it starts up faster than text editors like vi(1).
more
Don’t use more.