> PS. On a tangent, rethorically - baring bugs and security - at one point is (if ever) software "finished"?
“PS” originates from “post scriptum”, meaning “written after”. It doesn’t make sense to have it at the start of the text.
But to answer your question, yes, it is definitely possible for software to be done and finished. I’ve done it multiple times, where I have built something that does exactly what I set it out to do, it does it fast and without bugs and has been doing so for years and years with zero maintenance needs.
The general obsession with the idea that “software is never done, only abandoned” needs to end, it’s harmful to good software and its users.
Here’s millions more examples of finished software, in a single word: games.
A web search engine is never done because spammers never cease attempts to.game it in new ways, and because new phenomena keep appearing on the web, from presidents posting official news on twitter to the proliferation of AI-generated texts with subtly incorrect information.
Sad to hear.-
PS. On a tangent, rethorically - baring bugs and security - at one point is (if ever) software "finished"?
"We built this search engine. It works. The infrastructure has team enough to run it. But we have this huge payroll of people."
So "improvements" and "features" (and constant UI and UX changes) ...
... "enshittification" ensues.-
When is "good enough" ... good enough?