So one of the issues with Git is that just about any Git related command ends up being very chatty in terms of disk IO, i.e. a git show whatever isn’t just a single IO operation, it’s a whole bunch of them. When you end up running a forge for many users, this can wreak havoc in terms of performance and outages. Loading non-Git data (e.g. issues) from Git makes this even worse, especially if a project the size of say Kubernetes were to use it (e.g. they have about 50 000 issues in total).

How would Haxy handle that? That’s not some sort of “haha gotcha!” question, rather I’m seeing new forges pop up over the last two years or so but few of them seem to actually try to plan ahead/learn from all the scaling horror stories of GitHub, GitLab and others, so I’m curious if Haxy is any different in that regard.

score 1 · canonical

Bill Hicks and Earth Crisis mentioned in the opening line really got me feeling like I’m 15 again.

score 1 · canonical

I would love to know how vibey haxy is. The commits do not contain any info, there is no contribution file, but the author talks quite openly about their local models on YouTube. My first impressions of Haxy were positive, I like how opinionated (is there a better word for that?) it is, but I don’t like the lack of information otherwise.

Also, I loved that this project actually is as easy to build as the README describes (though that is at least a bit due to Zig as well, I guess).

score 2 · canonical