Some of the more enjoyable surfaces (for example, the grain of a fine mahogany table top or a Japanese sword) have an interplay between pattern and texture which, though two-dimensional, suggests the unseen internal three-dimensional array.
As we draw closer, we see that the three-faceted planes of the museum are fabricated out of rectangular panels made of white bronze that was poured directly into dammed forms on the concrete floor of the foundry, producing a surface texture similar to both metal and stone.
I’m now more inclined to attribute Looseleaf’s power to its visual texture than to some cognitive media-style abstraction. And the visual texture owes more to the beauty (yes, beauty!) of the original pdfs from the Vasulka Archive. Perhaps the demo is best understood not as a prototype generic tool, but as a specific curated experience in its own right, with form and content claiming equal importance in its overall success.
Even so, I think there are some general lessons that can be drawn from this demo:
Content is not inert
Visual texture lets content breathe
Visual texture lets the eye wander without losing itself
American cities seem like a product of industrial processes where older European cities seem like a product of human processes. This is because most American cities were built after and alongside the car and the industrial revolution – the design of cities took into account what was easily possible, and that guided the shape and scale of everything.
Software has similar analogues. There are software codebases that feel much more industrially generated than hand written, and they’re usually written in automation-rich environments fitting into frameworks and other orchestrating code.
…But despite the availability of cars, I still much prefer the scale and ambiance of European, human-scale cities, because ultimately cities are places humans must inhabit and understand. In the same way, I still much prefer the scale and ambiance of hand-written codebases even in the presence of heavy programming tooling, because ultimately codebases are places humans must inhabit.