Software is not abandoned anymore

At work we make use of hound code search. It is plain simple and fast. It is also virtually unmaintained for 3 or more years. So when some of our developers came to me with some questions (“Can’t it do X?”) my initial reply was: it is what it is, we cannot do much.

But then, I thought I should make some more use of my (work) Mistral subscription. So I switched to GLM-5.3 and (using pi) I did the following things:

  • I asked it to drop support for any repository that is not git (bye bye svn, etc)
  • I asked it to modernize Go (there have been a number of security releases for Go tooling)
  • I asked it to make it a multistage build
  • I asked it to make it a rootless container
  • I asked it to implement the features our developers wanted

Of the five tasks above I could easily and quickly implement the three. I would want to implement the fifth, but it would always take the least priority possible, so never and I would never deal with dropping non git repository support. It would also require better Go proficiency from me than I currently have.

Yes, within an hour we got our own fork that, for now, nobody else is using. But for this kind of software I am willing to keep working with our version. We could have switched to some fancier software, but that would come with its own operational tax – quite different from the fire and forget setup for hound (plus a Jenkins job that recreates the configuration each time a repository is added).

So that’a a true win for LLM maintained abandonware. The scope is clearly defined but the source code and the documentation. The added feature, if well defined, can be implemented without much hassle.

And life goes on.

Leave a Reply