When I first read As We May Think* as a teenager, I was astonished by how much it predicted of the computer age in 1945—but recently I’ve been feeling wistful about some pieces it predicts which never came to pass. [thread] *https://www.theatlantic.com/magazine/archive/1945/07/as-we-may-think/303881/ …
-
-
Bush also suggested that this web of links wouldn’t just be between others’ published works—that subordinates your own work to others’. Your own materials (drawings, drafts, voice recordings, etc) are also stops on the associative “trail.”
Show this thread -
If you want to arrange your own works relative to a disparate collection of others’ works, modern OSes offer folders and tags instead of links. In many cases, these are better: many associations form a clique or a tree, not a trail as Bush emphasizes.
Show this thread -
OS-level tags solve a problem Bush observes: that indexing systems usually assume there’s a “best” categorization of an item, but they often have many associations. You want many-to-many. But tagging a 100-page PDF or a 100-comp PSD isn’t very helpful. Memex links are page-level!
Show this thread -
But tags and folders are just sets. The structure is unordered, but your associations usually aren’t. It’s not just a theoretical problem: tags/folders are jumbled messes after a couple dozen items. Probably certain files are higher “degree,” but you’ll never know.
Show this thread -
Bush also describes how you could acquire trails from others—another notion we’re missing. Others’ trails could be applied to materials you already have, so you could see a colleague’s associative structures alongside your own, on the same files.
Show this thread -
Are there any good analyses of the structural reasons why we’re here and not there? Key problems with associative linking as attempted in past large-scale systems, etc? Other interesting attempts besides Xanadu? LiquidText is neat; fun to imagine OS-level adaptations… [fin]
Show this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.