Hacker News new | past | comments | ask | show | jobs | submit login

Warren Teitelman wrote about the history of Interlisp-D and other window systems in 1985, in the chapter "Ten Years of Window Systems - A Retrospective View" of the book "Methodology of Window Management" (the volume is a record of the Workshop on Window Management held at the Rutherford Appleton Laboratory's Cosener's House between 29 April and 1 May 1985).

Warren was the manager of Sun's Multimedia Group in which I worked on NeWS, and his contributions to programming environments and user interface design at Xerox PARC were important and underrated.

https://en.wikipedia.org/wiki/Warren_Teitelman

>Warren Teitelman (1941 – August 12, 2013) was an American computer scientist known for his work on programming environments and the invention and first implementation of concepts including Undo / Redo,[5] spelling correction, advising, online help, and DWIM (Do What I Mean).

Ten Years of Window Systems - A Retrospective View, by Warren Teitelman:

http://www.chilton-computing.org.uk/inf/literature/books/wm/...

>4.1 INTRODUCTION

>Both James Gosling and I currently work for SUN and the reason for my wanting to talk before he does is that I am talking about the past and James is talking about the future. I have been connected with eight window systems as a user, or as an implementer, or by being in the same building! I have been asked to give a historical view and my talk looks at window systems over ten years and features: the Smalltalk, DLisp (Interlisp), Interlisp-D, Tajo (Mesa Development Environment), Docs (Cedar), Viewers (Cedar), SunWindows and SunDew systems.

>The talk focuses on key ideas, where they came from, how they are connected and how they evolved. Firstly, I make the disclaimer that these are my personal recollections and there are bound to be some mistakes although I did spend some time talking to people on the telephone about when things did happen.

>The first system of interest is Smalltalk from Xerox PARC.

Alan Kay commented in email on that paper and Warren's under-appreciated work:

>Windows didn’t start with Smalltalk. The first real windowing system I know of was ca 1962, in Ivan Sutherland’s Sketchpad (as with so many other firsts). The logical “paper” was about 1/3 mile on a side and the system clipped, zoomed, and panned in real time. Almost the same year — and using much of the same code — “Sketchpad III” had 4 windows showing front, side, top, and 3D view of the object being made. These two systems set up the way of thinking about windows in the ARPA research community. One of the big goals from the start was to include the ability to do multiple views of the same objects, and to edit them from any view, etc.

>When Ivan went ca 1967 to Harvard to start on the first VR system, he and Bob Sproull wrote a paper about the general uses of windows for most things, including 3D. This paper included Danny Cohen’s “mid-point algorithm” for fast clipping of vectors. The scheme in the paper had much of what later was called “Models-Views-and-Controllers” in my group at Parc. A view in the Sutherland-Sproull scheme had two ends (like a telescope). One end looked at the virtual world, and the other end was mapped to the screen. It is fun to note that the rectangle on the screen was called a “viewport” and the other end in the virtual world was called “the window”. (This got changed at Parc, via some confusions demoing to Xerox execs).

>In 1967, Ed Cheadle and I were doing “The Flex Machine”, a desktop personal computer that also had multiple windows (and Cheadle independently developed the mid-point algorithm for this) — our viewing scheme was a bit simpler.

>The first few paragraphs of Teitelman’s “history” are quite wrong (however, he was a good guy, and never got the recognition he deserved for the PILOT system he did at MIT with many of these ideas winding up in Interlisp).

David Rosenthal (who worked on Andrew, NeWS, X10, X11, and ICCCM) replied:

Alan, thank you for these important details. I’d like to write a blog post correcting my view of this history — may I quote your e-mail?

Is this paper, “A Clipping Divider”:

https://dl.acm.org/doi/10.1145/1476589.1476687

The one you refer to?

David.

Alan Kay replied:

Hi David

Thanks very much! Your blog is a real addition to the history and context needed to really understand and criticize and improve today.

I would like to encourage you to expand it a bit more (even though you do give quite a few references).

I had very high hopes for Sun. After Parc, I wanted something better than Smalltalk, and thought Sun had a good chance to do the “next great thing” in all of these directions. And I think a number of real advances were made despite the “low-pass filters” and exigencies of business.

So please do write some more.

Cheers and best wishes to all

Alan

Don Hopkins replied:

Yeah, it was very sad that Sun ended up in Larry Ellison’s grubby hands. And I sure liked the Sun logo designed by Vaughan Pratt and tilted 45 degrees by John Gage (almost as great as Scott Kim’s design of the SGI logo), which he just sent out to the garbage dump. (At least Facebook kept the Sun logo on the back of their sign as a warning to their developers.)

I truly believe that in some other alternate dimension, there is a Flying Logo Heaven where the souls of dead flying logos go, where they dramatically promenade and swoop and spin around each other in pomp and pageantry to bombastic theme music, reliving their glory days on the trade show floors and promotional videos.

It would make a great screen saver, at least!

-Don

David Rosenthal posted on his blog:

History of Window Systems

https://blog.dshr.org/2021/03/history-of-window-systems.html

>Alan Kay's Should web browsers have stuck to being document viewers? makes important points about the architecture of the infrastructure for user interfaces, but also sparked comments and an email exchange that clarified the early history of window systems. This is something I've wrtten about previously, so below the fold I go into considerable detail.

I archived a discussion that started with Alan's reply to the question "Should web browsers have stuck to being document viewers?":

Alan Kay on “Should web browsers have stuck to being document viewers?” and a discussion of Smalltalk, NeWS and HyperCard

https://donhopkins.medium.com/alan-kay-on-should-web-browser...

>Alan Kay answered: “Actually quite the opposite, if “document” means an imitation of old static text media (and later including pictures, and audio and video recordings).”




Don, is it fair to Teitelman to say that after years of trying to get machines to DWIM, he finally enjoyed success with his dogs?


WIMP is like DWIM without Doo, but with Pee.

https://en.wikipedia.org/wiki/WIMP_(computing)

https://en.wikipedia.org/wiki/DWIM

>Critics of DWIM claimed that it was "tuned to the particular typing mistakes to which Teitelman was prone, and no others" and called it "Do What Teitelman Means" or "Do What Interlisp Means", or even claimed DWIM stood for "Damn Warren's Infernal Machine."

[==>]

>Warren Teitelman originally wrote DWIM to fix his typos and spelling errors, so it was somewhat idiosyncratic to his style, and would often make hash of anyone else's typos if they were stylistically different. Some victims of DWIM thus claimed that the acronym stood for ‘Damn Warren’s Infernal Machine!'.

>In one notorious incident, Warren added a DWIM feature to the command interpreter used at Xerox PARC. One day another hacker there typed delete *$ to free up some disk space. (The editor there named backup files by appending $ to the original file name, so he was trying to delete any backup files left over from old editing sessions.) It happened that there weren't any editor backup files, so DWIM helpfully reported *$ not found, assuming you meant 'delete *'. It then started to delete all the files on the disk! The hacker managed to stop it with a Vulcan nerve pinch after only a half dozen or so files were lost.

>The disgruntled victim later said he had been sorely tempted to go to Warren's office, tie Warren down in his chair in front of his workstation, and then type delete *$ twice.


Unfortunately DWIM was somehow intertwined with Interlisp macroexpansion so you couldn't disable it without losing macros.


I suspect the tales of "Do what Warren Means" are apocryphal. We're now used to the idea of wasting CPU cycles to compute possible completions of user entries. DWIM was just ahead -- and a way of deciding "conservative guesses".

I'd like to put together a demo of DWIM at its best and worst.


I need help please


What's this?

DWIM is evolving!

DWIM evolved into ChatGPT!




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: