windows
1º2º3º4º
Frosted and transparent
Irwin's window arrangement at the Dia:Beacon.
In addition to managing the flow of people in the spaces of the museum in order to maximize freedom of movement and choice, Irwin also modified the industrial window grids to create perceptual ambiguity, placing transparent glass in the inner four panes while using frosted glass for the outer panes. With this, Irwin solved the problem of either having the windows become a wall of glaring light, if all transparent glass was used, or having them become a claustrophobic muffling of space, if all frosted glass was used. Irwin's windows catch the eye in a back and forth oscillation between distant and proximal focus.
Of the plainest variety
It is unusual to find such mismatched elements on a single facade as this fine stonework coexisting with these stained and rotting shutters, on a house in the fortified town of Feltre, in the northern Italian province of Belluno.
Where considerable labour lies behind the cutting and fitting of the stone, the timber planks have been left in their raw state, with no paint or carved decoration. Even the iron hinges are of the plainest variety.
180. Window Place
Problem
Everybody loves window seats, bay windows, and big windows with low sills and comfortable chairs drawn up to them.
Solution
In every room where you spend any length of time during the day, make at least one window into a "window place".
We have lost our sense of intimate life
A Quote by Luis BarragánTake the use of enormous plate windows...they deprive our buildings of intimacy, the effect of shadow and atmosphere. Architects all over the world have been mistaken in the proportions which they have assigned to large plate windows or spaces opening to the outside. We have lost our sense of intimate life, and have become forced to live public lives, essentially away from home.
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.