2025-08-11 21:57 UTC
@zkat@toot.cat @xyhhx@nso.group @janl@narrativ.es @anildash@me.dm Oh for sure, I’m not against that at all. Things should cost money and magic externalities don’t work.
But I don’t think a lot of projects are prepared for the sticker shock of finding out how much their free GitHub CI compute costs. Also much of our CI and build systems infrastructure over the last decade have optimized for stateless computational waste because it was all free. Fixing that isn’t trivial and the ripple effects might be fairly large. We’ll see!
But yes, I’m okay with paying for things. I just think a lot of people are gonna have sticker shock when they see the price tag of that :)
Replies (2)
-
@anildash@me.dm 2025-08-11 21:59
@hazelweakly@hachyderm.io @zkat@toot.cat @xyhhx@nso.group @janl@narrativ.es I can say with a lot more authority than most that many people really, really do not have a good grasp of how much compute costs at scale. Folks take for granted the massive amount of subsidy that is happening across the industry for a whole host of ordinary developer tasks.
-
@kevin@mastodon.km6g.us 2025-08-11 22:45
@hazelweakly@hachyderm.io @zkat@toot.cat @xyhhx@nso.group @janl@narrativ.es @anildash@me.dm This part is really important. Entire generations of developers learned that it doesn't matter if your CI jobs are wasteful because it was all free.