minimalism
Less, but better
Raw size isn't enough
Omit needless words
Dieter Rams: As Little Design as Possible
Morioka Shoten
Minimum
A Book by John PawsonAdd Less
An Article by Cassidy WilliamsA few people have asked me what I did to make this [website] so fast.
The answer is: nothing.
I just didn't add anything to make it slow.I kept it simple.
The pages are pre-rendered.
The CSS is inlined.
I didn't add unnecessary javascript.
The work was done before you got there.Your websites start fast until you add too much to make them slow. Do you need any framework at all? Could you do what you want natively in the browser? Would doing it without a framework at all make your site lighter, or actually heavier in the long run as you create or optimize what others have already done?
Tanikawa House
A BuildingPhotos of the Tanikawa House, designed by architect Kazuo Shinohara.
Built in 1974, this summer house materializes the act of covering a piece of earth, making it an inhabitation only by means of a roof protecting the dirt soil of the ground. The house lies on a slope in a middle of a wood and grows through an exposed timber frame structure which supports a large pitched roof. Under the roof, a minimal section of the house located on a side hosts some specific living functions concentrated on two floors: a bathroom, a kitchen, a bedroom and a staircase. This section lies in parallel to the main “earth room” (or “summer room”) and overlooks it.
Do We Need This?
An ArticleUltimately this redesign has been a study in less, trying to dig deep and find out what it is I actually want for this site. A momentary visual “wow”, or quality content that is worthy of your attention? I decided on the latter, with less visual clutter it is far harder to try obscure bad or shallow writing behind a veneer of pretty images and effects. Posts may take longer to write but I hope this new design will push towards content that is worthy of your time.
The small web is beautiful
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?
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.
Features and complexity
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”.
Solving the problem of software bloat
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.
Raw size isn't enough
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.