Skip to main content

Computer History: Doug Engelbart

I went to a talk yesterday. It was the 40th anniversary of Doug Engelbart's 1968 "mother of all demos". In the demo, Engelbart demonstrated:
  • The first computer mouse
  • The first graphical user interface
  • The first personal, interactive, networked computer
  • The first use of hypertext (i.e. text with links)
I had heard about the demo but never watched it. It's available on YouTube, and it's definitely a must see. Doug had a grand vision of using the computer as a tool to help people accelerate how quickly they could solve problems. That goal has always fascinated me.

Robert Taylor, whose funding led to the creation of the ARPANET, told a pretty good joke, which he himself said was probably apocryphal. Rather than retell it, I grabbed a copy from here:
Whenever you build an airplane, you have to make sure that each part weighs no more than allocated by the designers, and you have to control where the weight it located to keep the center of gravity with limits. So there is an organization called weights which tracks that.

For the 747-100, one of the configuration items was the software for the navigation computer. In those days (mid-1960s), the concept of software was not widely understood. The weight of the software was 0. The weights people didn't understand this so they sent a guy to the software group to understand this. The software people tried mightily to explain that the software was weightless, and the weights guy eventually went away, dubious.

The weights guy comes back a few days later with a box of punch cards (if you don't know what a punch card is, e-mail me and I will explain). The box weighed about 15 pounds. The weights guy said "This box contains software". The software guys inspected the cards and it was, in fact, a computer program. "See?", the weights guy said, "This box weighs about 15 pounds". "You don't understand", the software guys responded, "The software is in the holes".
Allan Kay was also there. Allan is always fascinating to listen to. He said something that I thought was useful. He said that there is a difference between "new" and "news". "News" is when something happens and you get an update that it happened. News is simple and easy to assimilate. Something is "new" when it changes the rules of the game. When something is "new", it's impossible to fully understand the ramifications.

He had a great example. When the printing press came out, people thought it was "news". Suddenly, it was cheaper to print books. What they didn't understand was that it was actually "new". The printing press allowed ideas to spread more quickly, more broadly, and more accurately than ever before. It was impossible for them to understand just how profoundly the printing press would affect the world.

Comments

Ian Bicking said…
I haven't gotten through the entire demo yet, but I must admit on my geeky side I was really curious what the byte representation of the files is. How did all those pointers and structures work?

It also reminded me of Oberon, which is a kind of modern UI made by old guys (Wirth). The way he interacted with the text was similar, with the different points in the text and the somewhat more concrete nature of the text (as opposed to the more widgety system we're used to now).
jjinux said…
> I haven't gotten through the entire demo yet, but I must admit on my geeky side I was really curious what the byte representation of the files is. How did all those pointers and structures work?

Haha! Me too!

> It also reminded me of Oberon

Interesting. I had heard of the programming language, but I hadn't of the OS. I just read about it on Wikipedia. Thanks.
Ian Bicking said…
I personally found the Oberon UI far more interesting than the language or OS. I think because novelty in UI like that is uncommon. There's video game UI, but it's all bling and constraints, not information manipulation. I think new versions of Oberon might be using a more conventional UI.
jjinux said…
Ah, a man after my own heart. There isn't enough fundamental UI innovation, so seeing fundamental UI innovation is always such a treat.

Popular posts from this blog

Ubuntu 20.04 on a 2015 15" MacBook Pro

I decided to give Ubuntu 20.04 a try on my 2015 15" MacBook Pro. I didn't actually install it; I just live booted from a USB thumb drive which was enough to try out everything I wanted. In summary, it's not perfect, and issues with my camera would prevent me from switching, but given the right hardware, I think it's a really viable option. The first thing I wanted to try was what would happen if I plugged in a non-HiDPI screen given that my laptop has a HiDPI screen. Without sub-pixel scaling, whatever scale rate I picked for one screen would apply to the other. However, once I turned on sub-pixel scaling, I was able to pick different scale rates for the internal and external displays. That looked ok. I tried plugging in and unplugging multiple times, and it didn't crash. I doubt it'd work with my Thunderbolt display at work, but it worked fine for my HDMI displays at home. I even plugged it into my TV, and it stuck to the 100% scaling I picked for the othe

ERNOS: Erlang Networked Operating System

I've been reading Dreaming in Code lately, and I really like it. If you're not a dreamer, you may safely skip the rest of this post ;) In Chapter 10, "Engineers and Artists", Alan Kay, John Backus, and Jaron Lanier really got me thinking. I've also been thinking a lot about Minix 3 , Erlang , and the original Lisp machine . The ideas are beginning to synthesize into something cohesive--more than just the sum of their parts. Now, I'm sure that many of these ideas have already been envisioned within Tunes.org , LLVM , Microsoft's Singularity project, or in some other place that I haven't managed to discover or fully read, but I'm going to blog them anyway. Rather than wax philosophical, let me just dump out some ideas: Start with Minix 3. It's a new microkernel, and it's meant for real use, unlike the original Minix. "This new OS is extremely small, with the part that runs in kernel mode under 4000 lines of executable code.&quo

Haskell or Erlang?

I've coded in both Erlang and Haskell. Erlang is practical, efficient, and useful. It's got a wonderful niche in the distributed world, and it has some real success stories such as CouchDB and jabber.org. Haskell is elegant and beautiful. It's been successful in various programming language competitions. I have some experience in both, but I'm thinking it's time to really commit to learning one of them on a professional level. They both have good books out now, and it's probably time I read one of those books cover to cover. My question is which? Back in 2000, Perl had established a real niche for systems administration, CGI, and text processing. The syntax wasn't exactly beautiful (unless you're into that sort of thing), but it was popular and mature. Python hadn't really become popular, nor did it really have a strong niche (at least as far as I could see). I went with Python because of its elegance, but since then, I've coded both p