When we build, say, a business area in which all (or practically all) are engaged in earning their livings, or a residential area in which everyone is deep in the demands of domesticity, or a shopping area dedicated to the exchange of cash and commodities—in short, where the pattern of human activity contains only one element, it is impossible for the architecture to achieve a convincing variety—convincing of the known facts of human variation. The designer may vary color, texture and form until his drawing instruments buckle under the strain, proving once more that art is the one medium in which one cannot lie successfully.
Psychologists have noted that people tend to place greater artistic value on images when they can see the work that has gone into them — a tendency known as the “effort heuristic”. They are also more likely to connect emotionally with the work if they can detect the human hand, says Goldsmiths’ Chamberlain. “There’s an argument that if we see a brush stroke, we almost recreate it, and that’s part of the connection we feel with the artist — you can feel the intention.”
Perhaps to capitalize on this, some architects now show presentation drawings that look hand-drawn but are actually generated entirely by computer. “It’s totally fake,” says Brillhart. “They just take a computer image into Photoshop and put filters over it to make it look like it’s drawn by hand. It’s kind of amusing — instead of just sitting down and drawing for an hour, they spend eight hours making it look like a hand drawing.”
I believe that small websites are compelling aesthetically, but are also important to help us resist selling our souls to large tech companies. In this essay I present a vision for the “small web” as well as the small software and architectures that power it.
Why aim small in this era of fast computers with plenty of RAM? A number of reasons, but the ones that are most important to me are:
Fewer moving parts. It’s easier to create more robust systems and to fix things when they do go wrong.
Small software is faster. Fewer bits to download and clog your computer’s memory.
Reduced power consumption. This is important on a “save the planet” scale, but also on the very local scale of increasing the battery life of your phone and laptop.
The light, frugal aesthetic. That’s personal, I know, but as you’ll see, I’m not alone.
Niklaus Wirth of Pascal fame wrote a famous paper in 1995 called A Plea for Lean Software. His take is that “a primary cause for the complexity is that software vendors uncritically adopt almost any feature that users want”, and “when a system’s power is measured by the number of its features, quantity becomes more important than quality”.
But instead of just complaining, how do we actually solve this problem? Concretely, I think we need to start doing the following:
Care about size: this sounds obvious, but things only change when people think they’re important.
Measure: both your executable’s size, and your program’s memory usage. You may want to measure over time, and make it a blocking issue if the measurements grow more than x% in a release. Or you could hold a memory-reduction sprint every so often.
Language: choose a language that has a chance.
Remove: cut down your feature set. Aim for a small number of high-quality features. My car can’t fly or float, and that’s okay – it drives well.
Say no to new features: unless they really fit your philosophy, or add more than they cost over the lifetime of your project.
Dependencies: understand the size and complexity of each dependency you pull in. Use only built-in libraries if you can.
A few months ago there was a sequence of posts to Hacker News about various “clubs” you could post your small website on: the 1MB Club, 512KB Club, 250KB Club, and even the 10KB Club. I think those are a fun indicator of renewed interested in minimalism, but I will say that raw size isn’t enough – a 2KB site with no real content isn’t much good, and a page with 512KB of very slow JavaScript is worse than a snappy site with 4MB of well-chosen images.
...[Instead, it's about] an “ethos of small”. It’s caring about the users of your site: that your pages download fast, are easy to read, have interesting content, and don’t load scads of JavaScript for Google or Facebook’s trackers.