4 ms·
The subtitle says Ted was the inventor of hypertext, but in the interview he credits Doug Engelbart. You can hear him say it if you listen from 4:30 to 4:45. "
by andsoitis 4y ago
The subtitle says Ted was the inventor of hypertext, but in the interview he credits Doug Engelbart. You can hear him say it if you listen from 4:30 to 4:45.
"We thought computing would be artisanal. We did not imagine great monopolies."
Even though hindsight is 20/20, I'm still surprised that the power of network effects didn't occur to him (or whoever the "we" refers to).
"... artistic expression ..."
Reminds me a lot of when Jaron Lanier talks about how he envisioned VR.
- deleted 4y ago[deleted]
- ssivark 4y ago> Even though hindsight is 20/20, I'm still surprised that the power of network effects didn't occur to him (or whoever the "we" refers to). To unwrap that, the “power” of great efficiencies of scale, but also “weakness” from the lack of adaptability and resilience inherent to monocultures. The jury is still out on which way the balance swings — especially because the former manifests in “typical events” while the latter manifests in “tail events”. Post pandemic disruptions of logistical supply chains and supply-chain vulnerabilities in software, I think folks seem to (or at least ought to) be far more apprehensive of blindly submitting to network effects. In summary, it’s surprising to me that even in hindsight people seem so enamored with network effects to be blind to the cons.
- AlbertCory 4y agoRight. No one in 1963 was imagining billions of people with a computer. Watch "Mad Men" if you want to time-travel.
- gardenfelder 4y agoTed coined the term "hypertext"; he built a prototype Xanadu platform [1] which incorporated it. Engelbart created an editing system which used something like hypertext internally. Ted coined the term in 1963, along with "hypermedia" [2]; Engelbart published a paper in 1962 [3]; you can read it and decide for yourself whether he "invented" hypertext (by any name) in that paper. [1] https://en.wikipedia.org/wiki/Project_Xanadu https://en.wikipedia.org/wiki/Project_Xanadu [2] https://en.wikipedia.org/wiki/Hypertext https://en.wikipedia.org/wiki/Hypertext [3] https://dougengelbart.org/pubs/augment-3906-Framework.html https://dougengelbart.org/pubs/augment-3906-Framework.html Note that [1] says 1960 for Xanadu and [2] says 1963 for the term hypertext. Go figure. Edit: fixed typo
- andsoitis 4y agoFrom: > [1] https://en.wikipedia.org/wiki/Project_Xanadu https://en.wikipedia.org/wiki/Project_Xanadu Wired magazine published an article called "The Curse of Xanadu", calling Project Xanadu "the longest-running vaporware story in the history of the computer industry".[3] The first attempt at implementation began in 1960, but it was not until 1998 that an incomplete implementation was released. Ouch!
- jdougan 4y agoUnder the international hypertext accords of 2010, anytime the wired article is referenced, the rebuttal must be referenced also: https://web.archive.org/web/20001003011753/http://xanadu.com.au:80/ararat https://web.archive.org/web/20001003011753/http://xanadu.com...
- setr 4y agoWhat’s this letter he keeps referring to?
- jdougan 4y agoLetter to the Editor he sent Wired. Actually there have been several kicks at the can for rebuttals. Most recent ones are videos: Shorter Video: https://www.youtube.com/watch?v=-_-5cGEU9S0 https://www.youtube.com/watch?v=-_-5cGEU9S0 Feature length: https://www.youtube.com/watch?v=ASgjSxNdDqI https://www.youtube.com/watch?v=ASgjSxNdDqI
- scottLobster 4y agoAcademics rarely understand industry, it's just not what they're typically interested in. I got taught a lot of computer science theory in college, but at no point was I taught how commercial build systems work (unless you count make), and forget anything regarding scalability or manufacturing. Was actually quite frustrating for me when senior year rolled around and I still didn't fully understand how any of the theory I'd been shoving into my brain was actually used to create, say, a car or aircraft or even a calculator. At best I got a cursory series of lectures in scrum and assignments that required the use of Eclipse, and that was it. Even in the hardware-oriented EE side of the curriculum it was just working with basic prototype boards, nothing about the business side or mass production. It's not that my education was useless (far from it) but I wasn't taught how to "build" anything beyond toy projects until my first job. Granted, the people who had the knowledge to teach said methods were probably too busy making comparative bank in private industry, or perhaps were teaching business courses. Most academics are researchers, and researchers tend to be explorers, not builders.
- retcore 4y agoI have a hypothesis about this phenomenon of the software house monopolies, which is that wherever consistency of human interaction is beneficial, you get large concentrations of development, for reasons of human computer interaction being difficult and operating consistency and communication of skills network effects are created as a function of intrinsic human values propagation. Conceal the interface from direct user manipulation or the necessity for interaction for function, and individual or very small groups of artisans can be effective in extreme scale as is the case with much internet infrastructure and the Linux kernel. In the example of concentration of large development investment I'm thinking about, which is Microsoft Office, both kinds of network effects have been used to control and conflate different desires of monopoly, charades of open document formats and email protocol implementation (in this case the documentation is very good, practice however..) dancing between the lines of simpler competition and initiatives. Although the argument I'm effectively making turns out rather familiar to anyone who thinks of the turn of century software economy, I'm trying to replace economic theory with a suggestion that it's important to think about user applications for critical new infrastructure and protocols that can be developed simultaneously at comparable velocity alongside supportive infrastructure, instead of declaring standards and protocols that are left to capital markets to realize as products. Imagine if TBL had written a book recommendation and bartering spec as a backup for the paperless proposition of hypertext? Edit: fixed autocomplete error, removed "even" from last sentence.
- todd8 4y agoBack then the future was difficult to discern. I entered grad school in 1974 and at that time having a 300 baud modem (30 characters/second) at home was a luxury that only one of my friends could afford. I didn't have a personal computer. I was creative back then, and I remember envisioning VR very similar to today's VR. After studying visual displays and how they were projected on screens for pilots in flight simulators I presented an idea to my computer graphics class that we could put small displays on a helmet one for each eye and have motion and orientation sensors on the helmet to simulate what a pilot would see in 3D as he looked around the virtual cockpit. I said we could even develop multiuser experiences in a big gymnasium with a virtual landscape displayed in each participant's helmet displays. My professor dismissed the ideas as fanciful, and I moved on to other ideas. It was easy to imagine a future where lots of people owned personal computers and had modems that could be used to log into servers over dial-up lines; I remembered thinking that player verses player games would become a thing because the number of pairs of users online would grow much faster than the number of users [N(N-1) vs N]. But here, I was imagining a single multiuser server, not an internet. I was aware of the ARPA NET and had even tried out the PLATO timesharing system. I had a copy of Ted Nelson's interesting book of rambling ideas titled Dream Machines where he talked about hypertext, Xanadu, etc. I was also a teaching assistant for a telecommunications course where we talked about the possibility of fiber to the home replacing analog phone lines and providing bandwidth that could replace video rentals for entertainment. All of these hints foreshadowed the development of the internet, but I didn't see it and neither did any of my colleagues. The scale and importance of the internet just eluded me. As late as 1989 when I started a software company, it wasn't clear that the company should have it's own domain name!