I think they all have different philosophies in approaching the problem.

* https://juju.bi - Local-first architecture

* https://cursor.com/docs/origin - Scalable VCS backend (this is actually very easy to implement by others)

* https://tangled.org, https://radicle.dev - Distributed forges

* https://entire.com - Very agent-centric

GitHub CI is a very weird product. My team pays a decent bit of money for it, and we are nowhere near hitting the minutes limit, but at the same time we easily run into the storage limits, and the runner is incredibly slow?

On top of that the tooling is just... not good. The more I use it, the more I get annoyed at weird UX decisions, strange missing features, and the whole thing just being a giant bowl of spaghetti in general. You can easily spend days trying to make your workflows not suck just to realize halfway through that you could've been done already if you had just handwritten the damn thing in Bash.

We now live in the insane world where I am glad our tickets are still in the nightmare called Jira, because every day I get closer to asking management to switch to a forge which is actually functional - and with only CI and Git the transition would not be very difficult...

One of the things I didn't get to do at my last place before leaving was that I was putting together a proposal to beef up our CI infrastructure to be more cores per agent. I was trying to figure out the math to prove we would save money by doing so.

I had a batch process I became responsible for that ran on the same VM as an important production service and every once in a while it became a noisy neighbor. It ended up getting moved onto a much smaller cluster for the compute part of the operation after I did some pretty aggressive traffic shaping work to get the cost down by more than a factor of 10.

At one point I got the code into a shape where I thought I could just run it directly on the CI machine, and the lower CPU availability would be offset by the higher IPC overhead and cache misses. Problem was that it was still about 2.3x slower running on 1/3 as many cores. But those VMs idled for hours at a time while waiting for a 10 minute job to be started.

Near as I could figure, if we doubled the size of the instances the build agents ran on, I could shut down that cluster and just about offset the cost of the more expensive build agents exactly, and speed up quite a lot of builds in the process (many build steps do not parallelize but some do).

If one other team had a batch process they could just run directly on the CI machines, that would be a net reduction in operating costs. We had quite a few teams doing batch processing. CI servers have a lot of tricks you can use to queue up tasks rather than running them concurrently.

I think it's brilliant. I'm now paying $30 per month for Github actions as a duo shop... it's freemium working the way it should. Give them the first hit and all.

And yes, I need to optimize (and am), but they're already getting hundreds from little me. I even started going towards the CI doing browser walks, code tests, AI rework, etc. It saved me from having another dev machine.

Great stuff, powerful as all heck, and once you see the power it was—for me—impossible NOT to think of 6 other uses and blow through the free CI tier.

I still remember when TravisCI giving free CI to FOSS projects was revolutionary

In my self-hosted ones. Where are you building them??

Im guessing the lock-in is strong enough that they can eat the reputational hit while getting meaningful training data by subsidizing the free users.

Github has a decade of positive reputation to deal out, I don't see Grok or OpenAI jumping in and competing with that.

Maybe it is, but I know that lots of us used GitHub way before Actions launched. I think even if Actions wasn't free, GitHub would still have a massive advantage because it is the most well known place to host code, especially by less technical users (which is where I see a lot of finger pointing going with the increase in GitHub usage).

I would not be surprised if a serious amount of this usage is not user-intended and instead the LLM just inserts some sort of CI job off the bat and people roll with it.

Yes, we will be offering official CI (though nowhere near as free as GitHub). We will also support 3rd-party CIs (like https://buildkite.com, https://depot.com) & self-hosted runners (similar to GitHub)

If you hover over the green bar for today, the tooltip knows there's an incident.

if day.endswith('y'): return GREEN