order
Excursus: Homage to the Square^3
I know the deep night ballet and its seasons best
This order is all composed of movement and change, and although it is life, not art, we may fancifully call it the art form of the city and liken it to the dance—not to a simple-minded precision dance with everyone kicking up at the same time, twirling in unison and bowing off en masse, but to an intricate ballet in which the individual dancers and ensembles all have distinctive parts which miraculously reinforce each other and compose an orderly whole. The ballet of the good city sidewalk never repeats itself from place to place, and in any one place is always replete with new improvisations.
Same name in the same basket
Does a concert hall ask to be next to an opera house? Can the two feed on one another? Will anybody ever visit them both, gluttonously, in a single evening, or even buy tickets from one after going to a performance in the other?
In Vienna, London, Paris, each of the performing arts has found its own place, because all are not mixed randomly. The only reason that these functions have all been brought together in Lincoln Center is that the concept of performing art links them to one another. The organization is born of the mania every simple-minded person has for putting things with the same name into the same basket.
Complex systems of functional order
To see complex systems of functional order as order, and not as chaos, takes understanding. The leaves dropping from the trees in the autumn, the interior of an airplane engine, the entrails of a dissected rabbit, the city desk of a newspaper, all appear to be chaos if they are seen without comprehension. Once they are understood as systems of order, they actually look different.
The order of life
Like the housers who face a blank if they try to think what to do besides income-sorting projects, or the highwaymen who face a blank if they try to think what to do besides accommodate more cars, just so, architects who venture into city design often face a blank in trying to create visual order in cities except by substituting the order of art for the very different order of life.
The dishonest mask of pretended order
There is a quality even meaner than outright ugliness or disorder, and this meaner quality is the dishonest mask of pretended order, achieved by ignoring or suppressing the real order that is struggling to exist and to be served.
The Sense of Order
A Book by E. H. GombrichTendrils of Mess in our Brains
An Essay by Sarah PerryA ruin and a mess.
Watts observes that elements of the natural world – clouds, foam on water, the stars, human beings – are not messes, though the nature of their order remains inscrutable, and Watts doesn’t try to pin down its precise nature. Mess seems to be somehow a property perceptible only in the presence of human artifacts. Is this the result of some kind of aesthetic original sin on the part of humans, uncanny beings severed from the holiness of Nature? I hope not. “Humans are bad” is a boring answer.
How am I doing, wonder?
A Quote by Louis KahnForm comes from wonder. Wonder stems from our 'in touchness' with how we were made. One senses that nature records the process of what it makes, so that in what it makes there is also the records of how it was made. In touch with this record we are in wonder. This wonder gives rise to knowledge. But knowledge is related to other knowledge and this relation gives a sense of order, a sense of how they inter-relate in a harmony that makes all things exist. From knowledge to sense of order we then wink at wonder and say How am I doing, wonder?
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.