💾 Archived View for walve.net › thoughts › temperature-versioning.gmi captured on 2024-07-08 at 23:22:53. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2024-06-16)
-=-=-=-=-=-=-
Software is built to serve a purpose. Sometimes, that purpose is fulfilled, and no more substantial work is needed in the software. This is a software's absolute zero, when it's frozen, no substantial changes are done to it. It just works.
Of course, nothing "just works". Sometimes, bugs appear, maybe something can be improved in the performance department. As such, think wisely about what to freeze, maybe the specification your program works with is a good start. Even if you never freeze the codebase itself, anyone who uses it can rest assured the base of it won't change under their shoes.
As an example with one of my projects, Blit. It is largely frozen by now. I won't add any new instructions to it, I won't make any breaking changes to the assembler, it'll run in this state forever, or until the last bit of it dies.
That does not mean I won't fix any bugs that appear, or implement some idea that improves its performance. I just won't add any features.
Maybe one day, all software will last forever.