The thin lip of a teacup To give the building a sense of the delicacy associated with such crafts, as well as a feeling of warmth, I designed louvres from white porcelain panels, and used them to cover the outer walls. The louvres are tapered, to make their tips as fine as possible. (In fact, making tips as thin as possible is one of my key design principles: the thin lip of a teacup allows a better experience of the subtleties of tea - this is always at the forefront of my mind when I pay such close attention to edges.) Kengo Kuma, My Life as an Architect in Tokyo edges
An edge is an interface An edge is an interface between two mediums. Edges are places of varied ecology. There is hardly a sustainable traditional human settlement that is not sited on those critical junctions of two natural economies. Successful and permanent settlements have always been able to draw from the resources of at least two environments. Bill Mollison, Introduction to Permaculture As a kind of gateway edgesmedia
As a kind of gateway Historically, Japan's shrines have been built in order to worship the gods who live in the sacred mountains or seas; They don't reside in the shrine itself, but in the space beyond it. This belief that the spirits and deities exist beyond the confines of the shrine, and that the shrine itself acts not as a centre, but as a kind of gateway, is very different to the grand, imposing churches and cathedrals of Christianity. The majority of shrines are not found in the mountains or in the middle of the fields, therefore, but at the borders of mountain villages – which is to say, at what is seen as the edge of the mountains. The tori gate, marking the entrance to a shrine, indicates that there are gods on the other side of it. Kengo Kuma, My Life as an Architect in Tokyo An edge is an interfacePaths, edges, districts, nodes, landmarks religionedges
The small web is beautiful An Essay by Ben Hoyt benhoyt.com 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?Features and complexitySolving the problem of software bloatRaw size isn't enough Rediscovering the Small Web wwwmicrosites
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. performancesystemsconservation
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”. A Plea for Lean SoftwareSpeed is a featureRequirements proliferation featurescomplexity
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. minimalismcontentsize