Alan Kay's tribute to Ted Nelson at "Intertwingled" Festival

The Alto did things that even modern computers don't do as well. There's a demo I like to point at for this: ▶ this video Look how programmable this is by the user! Today's OSes and their division of software into "applications" erect barriers to software composition that don't need to be there.

OP here. Definitely some improvements... but (at least in my eyes) incremental. Notebooks are pretty sweet, but in the hands of very few. They're definitely growing in popularity, which is great. But even the "notebook" concept is a very limited "low pass filter" version of the visions of Engelbart, AKay, TN, etc. The video that AKay has been sharing around in the post than @dang linked to[0] is a great example of what's not-even-close to possible on today's systems. [0] ▶ this video

In the 'Tools, not Apps' part of the article they reference Michel Beaudouin-Lafon's talk 'A World Without Apps' which goes back in time and shows the Xerox Star operating system: link Another reference I usually bring up is Alan Kay's talk on smalltalk: ▶ this video My related comments on this, just to show other stories along this theme: - link - link - link

I love that this concept tries to separate content from apps. Ever since I saw some of the ways early GUIs differed from today's, I've had a feeling that we've lost something with the way apps in today's desktops are completely isolated from each other. The Alto let you compose data live from multiple windows kind of like a shell pipeline does for command-line apps: ▶ this video The Locus and Flows in this concept seem like they could enable a similar workflow, as data isn't confined to "apps" the way it usually would be.

Every time I see something like this, I'm also reminded of this demo of the Xerox Alto from a few years back. I'll link to the start of the most relevant piece: ▶ this video I'm always struck by the useful directions that desktop computers were going in the 70s, and how computing could be so much better than it is right now. But we've veered so off-course from all of this, away from composability and towards independent boxes ("applications") that can't talk to each other at all. Emacs is in some ways the best thing we have today in the other direction, but it pales in comparison to what's possible.

Well, something like the smalltalk-78 that Alan Kay demos here ( ▶ this video ) would be an ideal starting interface for e-ink based tablet.

> Thanks for sharing, I love these types of stories. Really makes me pine for the "old" days, and wonder if there's a parallel universe where technology took a very different route such that languages like APL, Lisp, and Smalltalk are used instead of JavaScript, Java, and C#, and what that world looks like. Easy, here is some time travel, "Alan Kay's tribute to Ted Nelson at "Intertwingled" Festival" ▶ this video "Eric Bier Demonstrates Cedar" link "Yesterday's Computer of Tomorrow: The Xerox Alto │Smalltalk-76 Demo" link However to be fair, Java, C# and Swift alongside their IDEs are the closest in mainstream languages to that experience, unless you get to use Allegro, LispWorks or Pharo.

It's out of the context of this thread, but we were quite sure that "simulation-style" systems design would be a much more powerful and comprehensive way to create most things on a computer, and most especially for personal computers. At Parc, I think we were able to make our point. Around 2014 or so we brought back to life the NoteTaker Smalltalk from 1978, and I used it to make my visual material for a tribute to Ted Nelson. See what you think. ▶ this video This system --including everything -- "OS", SDK, Media, GUI, Tools, and the content -- is about 10,000 lines of Smalltalk-78 code sitting on top of about 6K bytes of machine code (the latter was emulated to get the whole system going). I think what happened is that the early styles of programming, especially "data structures, procedures, imperative munging, etc." were clung to, in part because this was what was taught, and the more design-intensive but also more compact styles developed at Parc seemed very foreign. So when C++, Java, etc. came along the old styles were retained, and classes were relegated to creating abstract data types with getters and setters that could be munged from the outside. Note that this is also "simulation style programming" but simulating data structures is a very weak approach to design for power and scaling. I think the idea that all entities could be protected processes (and protected in both directions) that could be used as communicating modules for building systems got both missed and reject

To get another taste of the kinds of systems possible in the 70s, in spite of the constraints, see Kay's demo of a revived Smalltalk-78 system: ▶ this video (I believe this system is about 10-20K LOC software in total) Notes about the the revival are here: link

#Softwarish - I'm biased a bit more towards interface development: greg wilson - What We Actually Know About Software Development, and Why We Believe It’s True - link steve wittens - making webgl dance - the title is deceptive, it's in some ways a visual crash course in linear algebra - link glenn vanderburg - software engineering doesn't work - link chris granger - in search of tomorrow - link alan kay - tribute to ted nelson at intertwingled fest - ▶ this video bret victor - this is already mentioned but if I had to pick one it'd be 'the humane representation of thought' - link #Hardwarish: saul griffith - soft, not solid: beyond traditional hardware engineering - link deb chachra - Architectural Biology and Biological Architectures - link #Getting more meta in technology and history: James Burke - Connections

People often ask me "Is this a Dynabook, is that a Dynabook?". Only about 5% of the idea was in packaging (and there were 2 other different packages contemplated in 1968 besides the tablet idea -- the HMD idea from Ivan, and the ubiquitous idea from Nicholas). Almost all the thought I did was based on what had already been done in the ARPA community -- rendered as "services" -- and resculpted for the world of the child. It was all quite straightforwardly about what Steve later called "Wheels for the Mind". If people are interested to see part of what we had in mind, a few of us including Dan Ingalls a few years ago revived a version of the Xerox Parc software from 1978 that Xerox had thrown away (it was rescued from a trash heap). This system was the vintage that Steve Jobs saw the next year when he visited in 1979. I used this system to make a presentation for a Ted Nelson tribute. It should start at 2:15. See what you think about what happens around 9:05. ▶ this video Next year will be the 50 anniversary of this idea, and many things have happened since then, so it would be crazy to hark back to a set of ideas that were in the context of being able to be built over 10 years, and would be ridiculous if we didn't have in 30 (that would be 1998, almost 20 years ago). The large idea of ARPA/PARC was that desirable futures for humanity will require many difficult things to be learned beyond reading and writing and a few sums. If "equal rights" is to mean something over the entire pla

Alan Kay made scathing comments on the World Wide Web browser (reinventing a broken wheel) at length in a lecture "Normal Considered Harmful" for computer science students at University of Illinois Urbana-Champaign. For context: Alan himself invented WYSIWYG at Xerox PARC. He was present at "the mother of all demo's" by Douglas Englebart. Ted Nelson who invented hyperlinks and Xanadu got Alan in touch with his future wife [2] and Alan was there at Apple when Bill Atkinson made Hypercard. He mentions that when he told Tim Berners Lee about the much better work of Douglas Englebart, Tim was chagrined (that he had not read any of the papers about earlier and much better designs of 28, 25 and 20 years before the WWW browser). Of course Alan also discusses how the web should have been done. In short, it should be that when you click a hyperlink you load a virtual machine in a secure sandbox of a Operating System Kernel. The virtual machine would then render the (bitmap or vector) pages. Operating System 101, well known in 1965. Of course, Alan's team did implement this (several times). I can demo this if you contact me. Email me at morphle [at] ziggo [dot] nl for a video where Alan Kay, Douglas Englebart and Tim Berners Lee meet and talk about this at a forum discussion. You can ask me about anything related to Alan, Ted or Douglas, I maintain an extensive archive with all scientific papers, emails, talks, interviews and lecture video's. Alan, Ted and Douglas worked closely togeth