Retrospective shows Project Xanadu stalled due to missing design iteration and practical use cases

The retrospective concludes that Project Xanadu’s vision did not mature because the team never settled on a repeatable design process. Without regular iteration, ideas remained abstract and were not tested against real constraints. The author notes that his own workflow emphasizes rapid cycles to catch flaws early.

A former programmer described how translating a Smalltalk prototype to C++ required long compile times, far longer than today’s instant feedback. He also spent time wrestling with C++ quirks and build errors, which consumed valuable development hours. These delays illustrate how toolchain choices can dominate effort in low-resource environments.

Storage limits were another bottleneck; the party’s vintage PCs held roughly 50 MB, while modern projects like Gwern.net exceed hundreds of gigabytes. The disparity shows that early developers had to constantly juggle what could be kept online, limiting the scope of hypermedia experiments.

Adopting a similar vision today would still fail if designers skip iteration, ignore concrete use-cases, or overlook practical engineering limits such as build time and disk space. The retrospective warns that a compelling idea alone cannot overcome these constraints, and projects stall when they do not adapt to the hardware and workflow realities of their era.