Single file projects

A blog post of its own


Git Hosting migration is getting scary, first people were leaving GitHub, now they are leaving Codeberg. It’s not unfortunate, it’s a very costly decision. Each migration means you loose at least half of your users, and for those who follow you over, will have a deterioration in their workflow. Thanks to the great collaboration features these platforms provide, seriously, and thanks for making it harder to move off, now sarcastically.

What does it mean for me? Honestly I don’t have users so it doesn’t really matter, but it doesn’t mean I will never have. Since I can’t change the world, I decided to do some tiny steps on making my own work unlikely to break.

As the first step I’m reflecting about the tiny projects. People always like to do some little experiments, try something and eventually share it. Usually it becomes a repository somewhere getting dust. Not big of a project, but that also happens to shade the important ones. So why not to start with a better solution for them?

I present you: Single file projects.

This is a growing collection of projects that fit a single file and it’s source code is provided through this blog. The versioning and changelog is provided in the source code, alongside it’s license.

This is mostly for those kind of projects the author has monarchic control over the code, where no collaboration is expected, and which version control is overkill.

However, since the contents from this blog is version controlled, it means that even if I don’t use git for these projects, you can still get the diff between versions. Here is the link to it, so you don’t have to look up.