AI-assisted coding should fix open source, not flood it with to-do apps
We don't need more apps. We need better open source
Every weekend brings another AI-built habit tracker or note app, yet almost none of that energy goes into the open source software people actually depend on. Drawing on self-hosting Matrix, Paperless-ngx and Coolify for nonprofits, the author argues the real work is making existing tools faster, easier to install, friendlier to run and lighter — and that this patient, unglamorous labor suits AI well, provided someone checks every line and treats maintainers with respect.
A new to-do app usually helps the few people who find it. Making a tool millions already use 20% lighter helps all of them, every day.
- joshdata
> Pick one open source tool you use. Find the most annoying thing about installing or running it. Spend a weekend fixing it, with the people who maintain it. Then tell me about it.
My open source projects were barely sustainable when the few PRs that came in would fix actual, non-hypothetical, serious logic problems.
Now I've been seeing PRs like that, fixing annoyances, performance edge cases, or hypotheticals, across my open source repositories, and I don't have time for them. I especially don't have time to fix problems that probably nobody will ever experience, and yet they keep coming. I have not organized my life around triaging annoyances (let alone fixing them).
If the trend continues, I'll soon be forced to close repositories to contributions, or just stop maintaining the projects entirely. And I imagine that's the point a lot of maintainers are at.
- timbert
I think we need a new model of software delivery.
Here's my most-recent real-world problem: I wanted to plug in my midi controller keyboard and just play a piano, so I can practice my choral music. Very basic.
This turned into many hours over several days trying multiple DAWs, trying to get tehm to install, get them to run at all, get them to recognize my controller, get them to play a VST plugin...changing system settings, completely jacking up my sound, restoring it all again.
It was a nightmare.
So instead I fired up Claude, worked with it for about 3 hours, and now I have an *8-channel* VST player that supports all my hardware, and includes a snappy UI, with outstanding performance and sound. It's amazing!
I literally spent less time creating a custom solution than I did trying to get the off-the-shelf stuff to work. I could make my player OSS too, but the effort to do that is huge, for all the reasons this forum would understand.
Bespoke software avoids all of that and allows me to do what I want, with the environment I have. I don't have all the features of an FL Studio, but I have what I need, and that works for me, beautifully, at low cost and effort. What's not to like?
So maybe we should share OSS "templates" instead of full products, projects that are the barebones of a solution that you can clone, and have your LLM modify to suit your needs, on your platform of choice.
For example, perhaps my barebones VST player is mostly good enough for you, but you also want to […]
- linsomniac
> Pick one open source tool you use. [...] Spend a weekend fixing it
Beware: Your best path forward there may be, contrary to part of the thesis in this post, be to vibe code a replacement. There are a couple reasons why:
Expect to encounter significant push-back due to AI contribution. For example, I've had bug fixes to significant problems be rejected because "we are in the future going to be adopting a no-AI policy". Annoying because I spent my time working on it because they did not have a no-AI policy. Amusing to have another contributor contribute the exact same fix, like character for character, under a new PR (referencing my issue, so not done in isolation) and get it accepted.
There may also need to be sweeping changes to the project you are fixing -- which are going to be a burden to the maintainer and likely wouldn't be accepted because of that. A fork may be the way to go here, but also "vibe coding" a replacement might be the best option.
Earlier this year I build a replacement apt cache called apt-cacher-ultra. Part of it was because the existing apt-cachers had reliability issues, but a bigger part was I wanted something that would survive ubuntu.com being under a DDoS for a week or two. apt-cacher-ng was totally useless at that. The path I wanted to try was to have verified known good snapshots of the upstream, background refreshes, pre-fetching of known "hot" packages when the upstream refreshed. HUGE changes.
I've put 100 hours or more into this "vi […]
- delichon
Many apps have just been obsoleted by the new tech. I've tried hundreds of food logging apps and written a few. But none are nearly as good as my current daily driver, a Google spreadsheet wrapped by a GrokBot. I just tell it what I ate two or three times per day, voice or text, no attempt to normalize units or food names. It does all of that with nuance and I seldom have to correct anything. Major new features, like deriving a shopping list from the log, cost one short prompt. Or a running commentary by GaryTaubesBot.
This was just a sci-fi dream in 2022. Now I wonder whether apps are collapsing into an inference wrapped singularity.
- ValdikSS
We need to invent new definition to what many people expect when say "open source". Maybe use "Stewarded Open Source" coined by Dries Buytaert.
https://dri.es/license-only-versus-stewarded-open-source
The truth is: open-source doesn't come with any support, maintenance or feature request fulfilment by default.
By definition, that's just a code with no strings attached.
Do not expect maintenance or bug/security fixes by default from any project, unless stated otherwise, or there's at least some metrics which hint of maintenance.
We need SOCIAL.md to describe expectations from this project.
If that mindset is new to you, read this: https://raccoon.onyxbits.de/blog/bugreport-free-support/
- shmolyneaux
> I help progressive nonprofits with their tech for a living
This is the primary perspective behind this post, and that's going to look much much different than the devops roles a lot of us have.
> Too many apps need a database, a cache, a background worker, a reverse proxy and a long config file before you see a login screen
These apps need a database/cache/proxy/config because creating a fault-tolerant, performant, flexible system needs these things. The author wants everything to be a single binary running on a $5-a-month server. A lot of these open source tools could be updated to run in this mode, but that's not the configuration that's sustainable when there's a disaster.
You need to look at why these nonprofits are using open source projects in the first place. They probably want something free, and they probably want something with clear documentation. Maybe it's something that they're already used to. I would argue that AI-assisted (or vibe-coded) apps are cheap enough to fill this niche. Documentation is less important if the features of the app are much more narrowly-scoped. If they're already used to another app, then the vibe-coded one could be designed to provide a similar experience.
I've worked with non-profits that have struggled under the weight of the software they're using. Most often the problem is the software being too general in a way that doesn't model the domain well. Cheap custom software would help a great deal.
- poisonborz
Rarely do I see such a stupid headline on HN. I know where this comes from and I can sympathize with the author but from his subjective narrow experience he draws the wrong conclusions.
People post a bunch of throwaway microprojects. So what.
There are wide fields, industries, branches of society, communities, groups of friends left without proper apps to do "that thing". Not to do it better, but to do it at all. It is incredible that a much wider amount of people can engage in creating those apps now. That should be encouraged, and not gatekeeped into existing projects that are already drowning in PRs.
- gwt4life
I agree but open source needs to solve the monetization problem; developers need to eat.