October 2020

Memories

by Bret Victor

This entry is a stub, and will be expanded on a future archiving pass.

Realtalky state. Persistent statements visibly pinned to physical objects.

18:42

persistent visible memories

I reimplemented memories, as a hopefully-general-purpose mechanism for all virtual...

Later: page text, media, and everything else was moved into memories, so the memory database contains the entire state of a Realtalk system.

SYNCED MEMORIES This builds on the "persistent visible memories" email...

Earlier prototypes.

A few fun future features: Replicas Following from Luke's suggestions...

I found myself writing "persistent state" too persistently yesterday, so it was time to...

Progress on representing computational state in a visible, tangible way.

Room OS (2015) represents the entire state of the system in a live, editable, annotated viewer.

Database of meaning (2015) mocks up ideas for how the representation could go deeper.

Bigboard (2015) shows the state in context with the programs that produce it.

Organizing state (2016) mocks up ideas for representing state in Realtalk.

Realtalk Toys (2016) shows system state on a timeline.

Token table inspector (2016) shows system state on a timeline.

CV visualizer (2016) shows the values produces by a program as it runs.

The instantaneous state of a Realtalk system is a set of Statements (2017) made by physical objects.

The persistent state of a Realtalk system is represented as Memories (2020), which are sticky statements pinned to physical objects.

‹

›

▶