Source-last Programming
Authors/Creators
Description
Presentation, extended abstract, and associated artefact from LIVE 2026.
Abstract
Perhaps to build systems that are malleable and end-user programmable we need to rethink the relationship between runtime and development artifacts. It is our opinion that treating source code as the primary development artifact was the original sin that placed a one-way door between developer and user: when a saved format is authoritative, the tools that read and write that format are privileged, and everyone on the far side of the door is a user.
Lopecode is source-last: there is no external source code; the canonical representation is the live executing system. When source code is needed, functions are decompiled on demand starting from Function.prototype.toString(). Serialization becomes a projection to one of many formats: a standalone HTML file, a JavaScript IIFE or an ATProto PDS. Format-independence is a consequence of runtime-primacy. Because no format is canonical, editors, exporters and carriers are unprivileged userspace modules — a plurality of non-source editing surfaces that can be added after the program has started, without coordinating with each other.
We share three field episodes where the consequences of Lopecode's format agnosticism shone: shipping a tool into a locked-down corporate environment; liberating a running program from a notebook SaaS; and tunnelling an AI investigator into a third-party website.