It is now ten years since some of us wrote 2016’s Software and How it Lives On (SaHiLO) which set out a manifesto for durable, live software embedded in open contexts, worked on by unbounded communities of authors.
In the time since then, progress in reactive software, particularly in the JavaScript community, has now made it possible to tighten up some of the details of how this vision can be brought about. In that paper’s sections 4.4.6, and 4.4.7, entitled “Homeostasis rather than Execution” and “Mocks and a Taxonomy of Effects” it is announced somewhat diffusely, that we should seek an alternative to the dominant execution paradigm for organising our software, and that we should organise these designs around a clear schema identifying where side-effects may occur in a design.
[Read More]