The zero-cost fallacy: open-source software in the agentic era

I’ve stopped all my open source contributions and projects. I’ve now moved my resources to organizing and supporting communities like python Atlanta. My commitment was always the community and not the code. I also want to see what will companies do once open source closes shop and fewer people know how to program. It’s why I’m making sure there is a local support network for those of us who still want to stay in software over the long term.

>"For years, the software engineering industry has operated on a comfortable, perhaps lazy, myth: that open source software is an infinite, self-renewing public good that costs nothing to consume and requires nothing to sustain."

Since when? Open source projects have for decades offered paid support. Projects like Red Hat, Snort, Security Onion and others. I don't know anyone that has ever thought this. It's always been generally accepted that someone has to support it, either paid professional services or a full time employee with expertise.

This goes one of two ways.

Either the LLM public capability is not sufficient to positively contribute, or it is.

If it is not sufficient to positively contribute, open source projects become drowned in low quality contributions.

If it is sufficient to positively contribute, we end up with multiple implementations of open source projects.

Actually maybe it only goes one way.

I recently read Eric Raymond’s The Cathedral and the Bazaar. It was oddly sad to read.

The enthusiasm and optimistic view of open source and the future of software and craftsmanship. Looking at it in 2026.. incredibly sad.

Forget the bazaar. Back to the cathedral.

The agentic era definition of open source is garbage.

Software that is not open source, is proprietary software. Open weight models, are not open source. Binary blobs in a repo with an Apache license, is not open source.

Am I a retro-grouch? Probably. I guess it doesn't matter anymore what I think about it.

People need to stop yelling "Slop!" all the time and saying silly things like "every line of code was reviewed by a human". First, it's ridiculous. There is no possible way to verify that claim, determine what was or wasn't done after reviewing it, and there's no reason to review every single line. It's performative. I have a ton of stuff I haven't bothered contributing. Why? So I can deal with all the hate? When it was "many hands make light work" there was value in sharing the load. Now I've got a backhoe and it's not worth the hassle.

I love maintaining open source in an agentic world. I can be a complete asshole about contribution rules and coding standard as long as I define the AGENTS.md. The more strict the better and I can get good clean pull request without an endless back and fourth. I can even require updating the documentation!

An OCD dream but you need to embrace it and configure it or you would get "AI slop".

Open-source alternatives are being launched at an ungodly pace and they are really polished. All these comments about AI Slop are underestimating how good these builders have gotten and AI lets you iterate really fast. If the builder actually uses the software he's building, the feedback loop is really efficient.

I keep a directory of open-source alternatives and just in the past month, I've replaced applications I've used for years with open-source alternatives.

the issue with articles that try to analyze the state of open source and its sustainability and all that is that nothing about open source makes any sense if you just talk about it. Imagine you're transported to 1977 and you work at IBM and you try to tell them, oh hey I have an idea, how about the OS everyone uses for literally all commerce, communication, military, etc., you name it, will be written by one guy in his spare time and later maintained by tens of thousands of mostly unpaid volunteers. "Don't other companies try to copy it and sell it as their own?" "Well sure, but mostly it's better to use the free one everyone knows". Try selling your manager at IBM in 1977 that idea for new software. It would be impossible. It would be impossible today.

Trying to explain how the global economy and welfare of most of humanity is hugely dependent on free software production labor, without the advent of actually seeing a world where this actually happens, is just like when we try to explain something like consciousness. There is no explanation that makes sense. So predictions about new avenues of doom (like "MIT licensing was a huge mistake! we should have all been GPL!") similarly dont carry a lot of weight, because of course these predictions make perfect sense in the abstract, yet real world results don't line up at all.

Basically open source software is an emergent phenomenon, like consciousness or evolution, or perhaps even how very large language models suddenly seemed like real people. It's something that would never be predictable in its own absence, which means it will remain largely unpredictable how it will respond to ongoing changes such as "the open source authors and contributors now use programs themselves to produce more code".

The zero-cost fallacy: open-source software in the agentic era.

Here's my thoughts on this. It's back to open source, not open maintainer or open usage. I am producing lots of new code, i am publishing it. I am NOT interested in starting a project or having other people contribute. It's a cambrian explosion, the cost of adding features is basically zero. I'm going with "patching software is more common and we need tools around patching" rather than using other peoples stuff, just take what you want and fix it.

One stupid one is XRDP required some hack to go through VNC to connect to an existing session. I now have it built into xrdp and lets you pick the X11 session you on dial up and you're good to go. Why is this not a feature I dont know, but xrdp does it all now without vnc or anything. good stuff. i published it sure, i dont care if anyone uses it though.

Shift from passive consumption to active ownership.

Implement rigid supply chain auditing.

Formalize an open source contribution and patronage budget.

Well none of these help my bottom line directly so my boss will not approve.

I stopped reading at "load-bearing" and em dash.