>"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.
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.
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.
I tried to include examples but got flagged for it, it's grim two authors are willing to put their names to this while having the nerve to talk about "the industrialization of slop"
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.
>"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.
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.
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.
I stopped reading at "load-bearing" and em dash.
I tried to include examples but got flagged for it, it's grim two authors are willing to put their names to this while having the nerve to talk about "the industrialization of slop"
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.