The Smalltalk-80 Programming System

19K views · 14 years ago · demo · intermediate · historical

An 18-minute Xerox presentation of the Smalltalk-80 programming system from the early 1980s. It shows the windowed, mouse-driven environment with its class browsers and live objects that defined an influential way of working with software.

HN people include it in lists of historical GUI and programming environment videos, as a glimpse of what using a Smalltalk workstation felt like.

10 comments from Hacker News

p
@petilon2020 · in “Things That Turbo Pascal Is Smaller Than (2011)”
Hmm... you may be right. Here's the Smalltalk environment from 1980, it is pretty impressive: ▶ this video
RecommendsView on HN
g
@gkya2017 · in “The Smalltalk-80 Programming System [video, 18:44] (1983)”
Submitted the video to Hacker News.
RecommendsView on HN
p
@pjmlp2017 · in “Building a Command-Line Application with Crystal”
If you enjoy reading documents, BITSAVERS.ORG is a treasure mine full of lost knowledge. link Here you will find Xerox PARC, DEC, Burroughs, Apple, Sun, Borland,... old research documents, papers, manuals. In the context of static compilation, for example in MS-DOS, take Turbo Pascal 6.0 programmer's guide. link For some 8 bit love you can check ZX Spectrum and Atari archives. link link Next step is to get an emulator for any of those old OS/computers and try to follow along one of those books. Also there are some videos on YouTube showing those systems. "The Smalltalk-80 Programming System" ▶ this video "NeXT vs Sun" link "Steve Jobs internal demo of NeXTSTEP 3" link "Amiga Programming" link "Amiga Hardware Programming" link The Mother of All Demos" link Just a very tiny sample of videos
RecommendsView on HN
p
@pjmlp2014 · in “Web Starter Kit”
Self link Xerox Star User Interface link link Tektronix 4404 Smalltalk link The Smalltalk-80 Programming System ▶ this video The Final Demonstration of the Xerox 'Star' computer link Symbolics Hypertext Document link Warren Teitelman work at Xerox PARC link The Mesa/Cedar programming environment link Steve Jobs internal demo of NeXTSTEP 3, link Alan Kay on Xerox PARC work link link link
RecommendsView on HN
p
@pjmlp2014 · in “Shadow DOM”
Mainly videos Self link Xerox Star User Interface link link Tektronix 4404 Smalltalk link The Smalltalk-80 Programming System ▶ this video The Final Demonstration of the Xerox 'Star' computer link Symbolics Hypertext Document link
RecommendsView on HN
p
@pjmlp2013 · in “The Smalltalk-80 Programming System (Xerox Presentation)”
Submitted the video to Hacker News.
RecommendsView on HN
t
@trealira2023 · in “Should you split that file?”
> The problem I've seen with this idea is that in order for it to work, you have to be willing to add more metadata to your program, because programs themselves don't have the necessary data in them. You can make it mandatory to your language, but than just raises the friction for people trying to use that language. I'm confused by what you mean. Can you be more specific as to what sort of metadata that has to be embedded in the code would be needed? I've never used it, but watching this Smalltalk-80 IDE demonstration seems like it could be a workable idea. ▶ this video Edit: A more modern example using Pharo. You can see in the video that he's not accessing files, rather everything is sorted into packages and classes. link
CitesView on HN
p
@pjmlp2016 · in “Announcing Wolfram Programming Lab”
Xerox controlled the whole stack, they invented it for their systems. So these workstations where an whole stack OS. You can read about their implementations on the links I provided before. Additionally, you can get the original Smalltalk-80 from from Stephane's web site. link This is a very ruft idea how it felt to use a Smalltalk workstation: link ▶ this video The REPL was what is known in Smalltalk as transcript. Similarly the Interlisp-D workstation also had they own mixture of REPL and editing link Some of the ideas that lived on the Lisp Machines afterwards link link Mesa was a memory safe system programming language created at Xerox, as an evolution from Extended Algol to replace BCPL. Niklaus Wirth based his Modula-2 design on it. Shortly thereafter they updated Mesa into Cedar, which added support for RC with local GC for cycle collection. The system then got called Mesa/Cedar. It allowed the same interactive experience as the other workstations, but using a GC enabled systems programming language. The REPL provided nice features, like auto-suggestion when a typo would cause a compilation failure. It is also probably the first graphical debugger for a strong typed language. Any OS API could be used on the REPL by typing modulename.procedure , which could use other OS APIs to get its input from different sources. An idea Wirth adopted into Oberon. You can see how all three environments looked like here: link And yes, Powershell alongside .NET is probably the closest we have in modern computers to those systems. Followed by Swift Playgrounds and AppleScript on Apple systems. Although Apple also provided similar experiences with Common Lisp, Hypercard and their NewtonScript and Dylan.
CitesView on HN
p
@pjmlp2014 · in “Toward a better programming”
> I don't presume to know -- it's just the first system I came into contact with which has this concept. It was already present on the Xerox PARC systems. You can see a little bit of it here about Symbiotics, link at minute at minute 30. Or here for Smalltalk-80, ▶ this video
p
@pjmlp2013 · in “Tangle: a JavaScript library for reactive documents”
Except the original Lisp and Smalltalk environments are much more than a simple REPL. Sometimes I wish people would learn about computing history. Presentation from Kalman Reti about Lisp Machines, check the interactivity starting at 00:44:00 and how to introduce mouse sensitive images at 01:00:00 link Xerox presentations about Smalltalk-80 ▶ this video link link
CitesView on HN