DE version is available. Content is displayed in original English for accuracy.
Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
62% Positive
Analyzed from 897 words in the discussion.
Trending Topics
#open#source#software#code#slop#always#project#read#stuff#possible

Discussion (15 Comments)Read Original on HackerNews
There has been ever increasing consolidation in the hardware world along with an ever growing acceptance of restrictions by the public 'for our safety'.
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 narrative is not friendly to communities of people owning complex software by sharing work now, but neither was it then. If you believe it was all wrong, an incorrect formulation, then disregard it and do not despair to move on. If you think ESR got something right than nobody can see anymore, then your hope should be rooted in the knowledge of how much less than what's possible we are currently achieving
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 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.
But the flipside is of course users that are clueless won't now be stopped by "can't make a PR", they will throw prompt at AI and send it when the AI decides it's good enough
Both of these are true: we’re witnessing an unprecedented amount of slop, while also the tools get better and better.
So when talking about Open Source maintainer exhaustion, it’s because of the slop, not because if the great tooling.
AI is an amplifier, and in this case it amplifies the great asymmetry between contributor and maintainer.
Kind of like going to the app store and picking the app with the most downloads because the other option is looking at 400 different apps that may or may not do the same thing.
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.
Adding features was always the easy part. Maintaining the code OTOH is not going to be easier.
I see this with an experimental project I’m consciously vibecoding. The code base tends towards a spaghetti coded mess.
Of course you can put in some refactoring prompts and the AI will reorganize the code. But that makes it worse actually.
You have no mental model of the code and after a large refactoring even less.
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.
(Also, I'm never gonna give up my em dashes.)