Retrocomputing as preservation and remix

Abstract

Purpose The paper's aim is to describe the world of retrocomputing, a constellation of largely non‐professional practices involving old computing technology. It seeks to show how retrocomputing serves the goals of collection and preservation, particularly in regards to historic software, and how retrocomputing practices challenge traditional notions of authenticity. It then seeks to propose an alternative conceptualization and suggest new avenues for collaboration between retrocomputing practitioners and memory institutions. Design/methodology/approach The paper is based on extensive observation of retrocomputing projects, conducted primarily online. Findings Retrocomputing includes many activities that can be seen as constituting collection and preservation. At the same time, it is often transformative, producing assemblages that “remix” fragments from the past with newer elements or joining together historic components that were never combined before. While such “remix” may seem to undermine preservation, it also allows for fragments of computing history to be reintegrated into a living, ongoing practice, contributing to preservation in a broader sense. The seemingly unorganized nature of retrocomputing assemblages also provides space for alternative “situated knowledges” and histories of computing, which can sometimes be quite sophisticated. Research limitations/implications Retrocomputing challenges established notions of collection and preservation. A “situated knowledges” perspective provides a possible resolution. Practical implications Retrocomputing presents memory institutions (and libraries in particular) with an opportunity for new forms of collaboration in collection and preservation of software applications. Originality/value The paper puts at the center the ways in which retrocomputing challenges the established notions of collection and preservation. It offers alternative conceptualizations that suggest new forms of collaboration.

Cite this work

No public copy is stored for this record, so only the metadata is cited.

Stored only when both papers are in the corpus — 17 citations exist upstream.

Papers that cite the same references — the relational fallback while embeddings are still backfilling.