Yanagi Sōetsu
What is Pattern?
Handicrafts and Sesshu
Okinawa's Bashofu
A Painted Karatsu as Food for Thought
Recently there is a tendency to pursue distortion in art, but in the case of this jar, natural deformation has raised distortion to the level of spontaneous beauty.
Woodblock Prints
An Essay from The Beauty of Everyday Things by Yanagi SōetsuIt seems to me that many printmakers are suffering under a delusion. Looking at current trends, it appears that recent prints are simply copying fine art and painting. Some printmakers are working in the nanga style of painting. Others are attempting to reproduce the effects of oil. Some cleverly contrived prints are often difficult to distinguish from paintings done with a brush. The question arises: Why are these printmakers working in the medium of woodblock printing at all?
For prints to follow in the footsteps of painting has very little meaning. The art of the brush and palette should be left to the brush and palette.
Seeing and Knowing
An Essay from The Beauty of Everyday Things by Yanagi SōetsuThe results of intuition can be studied by the intellect, but the intellect cannot give birth to intuition.
The Japanese Perspective
An Essay from The Beauty of Everyday Things by Yanagi SōetsuGenerally speaking, the Western perception of art has its roots in Greece. For a long time its goal was perfection, which is particularly noticeable in Greek sculpture. This was in keeping with Western scientific thinking; there are no painters like Andrea Mantegna in the East. I am tempted to call such art ‘the art of even numbers’.
In contrast to this, what the Japanese eye sought was the beauty of imperfection, which I would call ‘the art of odd numbers’. No other country has pursued the art of imperfection as eagerly as Japan.
The Beauty of Kasuri
An Essay from The Beauty of Everyday Things by Yanagi SōetsuThe Characteristics of Kogin
An Essay from The Beauty of Everyday Things by Yanagi SōetsuThe Beauty of Miscellaneous Things
An Essay from The Beauty of Everyday Things by Yanagi SōetsuWashi
An Essay from The Beauty of Everyday Things by Yanagi SōetsuHandmade washi (traditional Japanese paper) is replete with appeal. Looking at it, touching it, fills me with an indescribable sense of satisfaction. The more beautiful it is, however, the more difficult it is to put to use. Only a master of calligraphy could possibly add to its beauty; it is exquisite just as it is. This is wonderfully strange, for it is merely a simple material. Yet plain and undecorated as it is, it is alive with nuanced beauty. Good washi makes possible our most ambitious creative dreams.
What is Folk Craft?
An Essay from The Beauty of Everyday Things by Yanagi Sōetsu
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.