VLDB 2026 Research / reviewers in the wild / expert
Ted Kaehler
dblp:23/6704
· DBLP profile ↗
3ranked-venue papers
1as first author
0since 2021 · last 2011
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 3 · 1 first-author
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Software engineering, system software, and programming languages
1 paper |
Runtime systems and virtual machines · 75% Programming languages and type systems · 25% | |
| Computer architecture, parallel and distributed computing, and storage systems
1 paper |
Memory systems · 100% |
Topics — the 5 heaviest of 7, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Runtime systems and virtual machines
garbage collection |
0.0 | 1 | 1997 | Back to the Future: The Story of Squeak - A Usable Smalltalk Written in Itself · OOPSLA 1997 |
Runtime systems and virtual machines › garbage collection
incremental garbage collection |
0.0 | 1 | 1997 | Back to the Future: The Story of Squeak - A Usable Smalltalk Written in Itself · OOPSLA 1997 |
Programming languages and type systems
language implementation |
0.0 | 1 | 1997 | Back to the Future: The Story of Squeak - A Usable Smalltalk Written in Itself · OOPSLA 1997 |
Runtime systems and virtual machines
virtual machine implementation |
0.0 | 1 | 1997 | Back to the Future: The Story of Squeak - A Usable Smalltalk Written in Itself · OOPSLA 1997 |
Memory systems › memory management
virtual memory |
0.0 | 1 | 1986 | Virtual Memory on a Narrow Machine for an Object-Oriented Language · OOPSLA 1986 |
Methods — techniques the papers use, named apart from their topics
translator to c · 0.0bitblt · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2011 | Worlds: Controlling the Scope of Side Effects
Alessandro Warth, Yoshiki Ohshima, Ted Kaehler, Alan C. Kay |
ECOOP | 3 |
| 1997 | Back to the Future: The Story of Squeak - A Usable Smalltalk Written in ItselfabstractSqueak is an open, highly-portable Smalltalk implementation whose virtual machine is written entirely in Smalltalk, making it easy to. debug, analyze, and change. To achieve practical performance, a translator produces an equivalent C program whose performance is comparable to commercial Smalltalks.Other noteworthy aspects of Squeak include: a compact object format that typically requires only a single word of overhead per object; a simple yet efficient incremental garbage collector for 32-bit direct pointers; efficient bulk-mutation of objects; extensions of BitBlt to handle color of any depth and anti-aliased image rotation and scaling; and real-time sound and music synthesis written entirely in Smalltalk. Daniel H. H. Ingalls, Ted Kaehler, John Maloney, Scott Wallace 0002, Alan C. Kay |
OOPSLA | 2 |
| 1986 | Virtual Memory on a Narrow Machine for an Object-Oriented LanguageabstractLOOM (Large Object-Oriented Memory) is a virtual memory implemented in software that supports the Smalltalk-80(™) programming language and environment on the Xerox Dorado computer. LOOM provides 8 billion bytes of secondary memory address space and is specifically designed to run on computers with a narrow word size (16-bit wide words). All storage is viewed as objects that contain fields. Objects may have an average size as small as 10 fields. LOOM swaps objects between primary and secondary memory, and addresses each of the two memories with a different sized object pointer. When objects are cached in primary memory, they are known only by their short pointers. On a narrow word size machine, the narrow object pointers in primary memory allow a program such as the Smalltalk-80 interpreter to enjoy a substantial speed advantage. Interesting design problems and solutions arise from the mapping between the two address spaces and the temporary nature of an object's short address. The paper explains why the unusual design choices in LOOM were made, and provides an interesting example of the process of designing an integrated virtual memory and storage management system. Ted Kaehler |
OOPSLA | 1 |