HackerTube.dev

Xerox Star User Interface: An overview

ACM SIGCHI · 20.4K views · 2021-02-09 · 17:10

Open on YouTube ↗

If playback is restricted in your region, try opening the original video. Use Mark watched to add it to your marked videos.

Overview

A 1982 Xerox PARC film, presented at CHI '90, in which Star designers David Canfield Smith and Charles Irby give an overview of the Xerox Star interface. It shows the document-centric, icon-and-window office system.

On Hacker News

Cited as the primary historical demo of the Star UI whenever its influence on the Mac and Lisa or document-centric design is discussed.

Discussed on HN; no positive recommendation is recorded in this export · HN mentions 2022–2025

Topics

Search by tags

What people said

leoc · 2025-08 · Reference

Here's a head-to-head video demonstration of the Lisa and the Xerox Star 8010: [LINK] And a dedicated video on the Star: [VIDEO] .

Read the original HN comment ↗
bane · 2024-08 · Reference

The history of Operating System development is really interesting in that the decisions of what the atomic element of the system are (files, documents, or applications) lock all future development into a certain path, but all the choices not made then have to be somewhat retrofit into the design. For decades systems have dwelled in a kind of morass where they seem to focus on trying to implement different variants of the other two, with one of these atomic elements as the core concept. For example, the dominant atomic concept in Xerox Star was the document [1]. Documents are an abstraction just above files. A webpage is a document, but is made up of numerous files like the graphics, fonts, executable scripts, etc. Document oriented systems like Star also deemphasize applications. The system is supposed to open up the correct application(s) when you choose to interact with a document. But even with this as the core abstraction, the system still had to provide methods to work directly with files and applications. Other systems, like Plan 9, nixes, MS-DOS, CP/M, etc. focus on the file as the atomic primitive and try to build around that. But when things moved to GUIs, many of the development teams focused on the Applications. Windows 3.x famously only showed users organized collections of applications, with file management as just another application. But Windows 3.x was sitting on top of DOS which oriented itself around files. The nixes in the meanwhile forgot about documents a

Read the original HN comment ↗
lispm · 2023-07 · Reference

> The Xerox Smalltalk-80 GUI Was Weird "Weird" means only that you haven't used other similar UIs. Smalltalk 80 was a development environment. There were applications written in it with more extensive UI examples. > At first glance, this looks incredibly similar to something like the desktop of the Apple Lisa or early Mac OS. Not at all. But the Smalltalk 80 UI was only one of several that were developed. It would be better to compare the Mac OS UI to the office system from Xerox. > The first thing is that the Smalltalk environment wasn't really an operating system the same way something like Mac OS was. It’s more like an IDE that runs on bare hardware. The Mac hadn't also much of an OS. It was like running c/pascal/assembler code on bare hardware with a loader and a system library. > You can’t even move or resize a window by clicking and dragging. The "Direct manipulation interface" was made popular by the Mac. [LINK] A good idea to compare those systems is to check how early applications looked and worked. On the Mac that would have been MacPaint and MacWrite. You'll find earlier such applications for the Xerox systems, too. The Xerox Star UI: [VIDEO] [LINK]

Read the original HN comment ↗

Sources

Video by ACM SIGCHI, played through YouTube.

Data and selection notes

HN summaries and labels may contain AI errors. HN dates refer to discussions, not video publication.

HN Library: HackerTube export (2026-10-31) and open-index/hacker-news. Upstream summaries and classifications may contain AI errors.

Views, duration and playback status refresh separately from the published catalog. When an update fails, existing data remains visible.

Selection checks
  • SaaS & AI candidates: Topic keywords do not match
  • Editor-approved picks: Editorial review is required

Rule matches identify candidates. They do not guarantee video quality or financial results.

About the library and its sources