Restrained beauty Braun design had a beauty that was more than skin deep. It would be wrong to say that because the Braun approach spurned fashion in an ongoing quest for functional and useable perfection, it ended up with this beauty by accident. There is a very strong aesthetic sense in both the proportion and materials of nearly all the products of the Rams era. They have a ‘restrained beauty’, he admits. Braun products designed by Rams and his team have a haptic aesthetic as well: when you pick them up, handle them, and use them as the tools they are supposed to be, you become aware of the effort that has gone into making them sit comfortably in the hand, of the texture, weight and balance they possess, and of the satisfying click of the control buttons. Sophie Lovell & Dieter Rams, Dieter Rams: As Little Design as Possible Such an unholy alliance beautytouchtexture
This tactile form of doodling Paper clips have also served as objects of more inwardly directed aggression by providing something for the fingers to twist grotesquely out of shape during phone calls, interviews, and meetings. This tactile form of doodling may consume only a fraction of the twenty billion paper clips produced each year, but it underscores the almost limitless functions to which a single form can lead. Henry Petroski, The Evolution of Useful Things In ways you didn't anticipateAll sorts of ways to use the machineStretching the product drawingtouch
What is this static modernism? Why can't office buildings use doorknobs that are truly knob-like in shape? What is this static modernism that architects of the second tier have imposed on us: steel half-U handles or lathed objects shaped like superdomes, instead of brass, porcelain, or glass knobs? The upstairs doorknobs in the house I grew up in were made of faceted glass. As you extended your fingers to open a door, a cloud of flesh-color would diffuse into the glass from the opposite direction. The knobs were loosely seated in their latch mechanism, and heavy, and the combination of solidity and laxness made for a multiply staged experience as you turned the knob: a smoothness that held intermediary tumbleral fallings-into-position. Few American products recently have been able to capture that same knuckly, orthopedic quality. Nicholson Baker, The Mezzanine The door handle is the handshake of a building modernismdoorstouchobjects
Time turned into shape A pebble polished by waves is pleasurable to the hand, not only because of its soothing shape, but because it expresses the slow process of its formation; a perfect pebble on the palm materializes duration, it is time turned into shape. Juhani Pallasmaa, The Eyes of the Skin: Architecture and the Senses timetouchform
Vision reveals what the touch already knows Juhani Pallasmaa, The Eyes of the Skin: Architecture and the Senses touchvision
Crown A Poem by Kay Ryan www.poetryfoundation.org Too much rain loosens trees. In the hills giant oaks fall upon their knees. You can touch parts you have no right to— places only birds should fly to. naturetreesmelancholytouch
To see, to caress A Quote by Johann Wolfgang von Goethe The hands want to see, the eyes want to caress. The Eyes of the Skin: Architecture and the Senses touchseeing
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