We don't need more apps. We need better open source (jordankrueger.com)

311 pointsby pandemicsoul4 hours ago203 comments

joshdata 4 hours ago

> 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.

cwel 4 hours ago

> to fix problems that probably nobody will ever experience

Have you considered that the person submitting the PR to fix said problem has themselves experienced it? I find that is most often the case. But there is definitely an increase in the "performance edge cases, or hypotheticals" framing, where I am equally befuddled/too tired.

awakeasleep 4 hours ago

What makes you think a person is submitting the PR

cwel 4 hours ago

Poor phrasing on my part, I should have said "the person involved in the PR", "the one behind the prompt".

kuriho 3 hours ago

not the parent, but I received one PR adding a new feature to my and similiar projects at the same time. When I questioned the use case the PR sat around until it was closed months later. Hardly a real user.

j16sdiz 3 hours ago

Before AI, I have submit PR band-aids bugs I personally experienced, but don't bother enough to fix it properly. When the maintainer ask about it, I move on and ignore it. I just don't care. Some maintainer found them useful, some don't.

I came from the "free software as in free puppy" camp. I would stop by to play with the puppy, but I won't feed it.

I guess if I do the same today, I might submit a better-than-band-aid fix from LLM. You would probably think I am not a real user.

stackghost 3 hours ago

Sounds more like a real user than an LLM, which would have given you a 4-heading treatise where the third heading was some variation on “Why this matters”.

matkoniecz 3 hours ago

> Have you considered that the person submitting the PR to fix said problem has themselves experienced it?

I had multiple PRs for entirely hallucinated problems.

Or where no human ever looked at project or PR and were just attacking open source projects with spam PRs pretending to be contributions. Not sure whether it was out of malice or done for some other reason. Maybe they were mistakenly thinking it is helpful?

shagie 2 hours ago

> Not sure whether it was out of malice or done for some other reason. Maybe they were mistakenly thinking it is helpful?

I believe a fair bit of this is an attempt to gain numbers where quantifiable numbers are advertised on otherwise indistinguishable resumes (with the corresponding belief that those numbers make differences in filtering or hiring decisions).

I base that on having seen people in the days of old put their Stack Overflow reputation on resumes thinking that having a rep of 4321 will be more likely hired than someone with a rep of 1234.

Having "210 accepted PRs on GitHub" (they believe) would appear to make them a more productive / less risky hire than someone who hasn't done any.

---

This is really a case of indistinguishable resumes where nearly everyone in the pool went to the same college, same internships, same capstone project, and maybe the same first year or two of professional experience.

JDups an hour ago

There are job applications that list having a certain amount of contributions to github projects as a requirement. Encourages useless spam. Also funny the implication that only projects on github have any worth.

shagie an hour ago

That wouldn't surprise me in the slightest. I see it with applicants for a position that doesn't have GitHub contributions listed as either a requirement or a nice to have.

I could see it as a "proof of familiarity with CI and expectations for a PR", though for applicants that are spamming the process with poor PRs (and people posting poor Q&A on Stack Overflow back in the day), this often hurts them more than it helps as its a demonstration of what they are going to be doing if they are hired (I've already got too many poor quality PRs to review, your PRs would not reduce the amount of time that the reviewer would need to spend).

levkk 3 hours ago

That's not the case all the time anymore. It used to be. But it's not now.

So yeah, I've considered it and eliminated it for most PRs we used to get. Because no, a 2nd year student in university did not run into an obscure edge case in production that none of my 1M+ QPS users did.

zahlman 2 hours ago

Sure, but maybe the reason you're getting PRs is because you have 1M+ "QPS users", whereas I can't even think off the top of my head what QPS stands for.

Conscat 3 hours ago

And personally I have never once opened a PR for any issue I didn't personally experience. Even when I used an LLM to assist, I've only worked on things I personally needed.

riedel 2 hours ago

Actually IMHO, we need better automatic build system integration with feature management. How cool would it be if the average user could vote with their feet if something is needed. Once there is enough adoption and no negative test reports consider merging it.

I guess also AI managed canary l releases could be an option IMHO that combine open PRs.

awakeasleep 4 hours ago

Remember the "Savage Reservation" in Huxley's Brave New World?

We need the equivalent of that for open source software maintained by people from before 2004.

tombert 4 hours ago

Just make a contributor license agreement based on Benedictine doctrine. At least one very successful FOSS project does that: https://sqlite.org/codeofethics.html

BarryMilo 3 hours ago

> First of all, love the Lord God with your whole heart, your whole soul, and your whole strength.

I rolled my eyes so hard I died.

linsomniac 3 hours ago

>My open source projects were barely sustainable

AI can help with that! Give an agent some rules, like via a skill for the project, and then point it at the PR/Issue for triage to determine if it's one that fits the rules for auto-closing (already reported and decided WONTFIX, for example). Have it run this across all your repos.

Have the AI tooling do the heavy lifting of reproduction and benchmarking. One of my projects is fairly complicated and one user ran into some problems which he could describe the situation that caused it, but was light on any other details: my apt package cache was slow to serve the PHP update to his users. I asked AI to try to reproduce it: Set up a repo, set up different versions of my cache, have a client pull it, put an updated package in there, and have a client pull it again under different configurations. This could have taken me hours to do myself. AI did it with ~2 minutes of my effort.

>I have not organized my life around triaging annoyances

Then don't. AI can help with the triaging. Or, I give you permission: Close the repo for contributions. If you don't have time to maintain it, let people know, so they can fork or replace it. It sounds like your repos are already closed to contributions, due to lack of time/attention. That's fine, don't feel bad, just go ahead and make it official.

matkoniecz 3 hours ago

> AI can help with that! Give an agent some rules, like via a skill for the project, and then point it at the PR/Issue for triage to determine if it's one that fits the rules for auto-closing (already reported and decided WONTFIX, for example). Have it run this across all your repos.

For me it was a bit useful but it has not offset even 10% of damage caused by LLMs

and is solving least important problem

yeoldeprogramme 3 hours ago

“ he could describe the situation that caused it, but was light on any other details”

You are too nice. Anyone who isn’t going to spend time to explain an issue should be automatically rejected.

We’re in this ugly situation where AI causes the problem and people’s idea to fix it is throw in more AI.

Just like throwing technology at climate change when our own obvious habits are destroying the planet. Let’s move to Mars.

flatline 3 hours ago

You can say, "go off and fork the project", and you'll get 20 forks, each one person's pet PR applied, and no more future progress without a dedicated maintainer triaging and coordinating all this stuff in one place. You are asking projects that are surviving but not necessarily thriving to simply die. And for what? To satisfy downstream developer demand for their AI-generated contributions to be accepted?

Not all contributions are equally valuable, and that is notwithstanding AI use. AI facilitates volume but not necessarily quality. Why should anyone spend resources benchmarking and reproducing a non-issue, or a PR that will not otherwise pass muster? We can automate a lot, but human judgment is still critical in making things to be used by humans.

hardbass 2 hours ago

Of course. So do you want a Grand Vizier to ban forks that are not valid so software runs the way it should be run?

zem 2 hours ago

how does the presence of those forks contribute to the project's demise in any way?

hardbass 13 minutes ago

It was common point of irritation and frustration to see projects like GNOME and Mozilla make bs excuses for not fixing bugs and randomly closing bug requests. People writing their own forks and patches were hailed as doing a worthy act. After AI, suddenly those people are all evil and the GNOME and Mozilla attitude is correct.

linsomniac an hour ago

>you'll get 20 forks, each one person's pet PR applied

Sure; if the primary repo goes unmaintained, and nobody else steps up to maintain a fork, yes you might get multiple forks that solve a specific users individual issue. I'm not sure there's a way around that.

The comment I was replying to sounded like someone who was unavailable to handle non-AI requests as well. AI contributions is making it worse, though my biggest projects haven't been hit by it yet <knock on wood>.

Low quality contributions is a very real problem, I agree with that.

necovek 3 hours ago

By running automated AI agents on untrusted inputs (PRs from strangers on a public repo), you open yourself up to attacks. And you could be spending money for somebody else.

epistasis 3 hours ago

The only attacks possible would be the tools given to the agent.

swiftcoder an hour ago

Assuming it can't perform a sandbox escape, at any rate. Maybe a Jev-like decision model would be a better idea.

epistasis 14 minutes ago

Or just don't allow tools, write a simple python script that uses the API and doesn't do tool calls, etc. etc. etc.

Table stakes for being an engineer these days should include knowing how to control LLMs, it's as fundamental as a working knowledge of databases. One doesn't need to know how design a data model from scratch or code up that python script using the OpenAI API from memory, but should know the general shape of what's possible and how to look it up.

linsomniac an hour ago

Agreed and this is a very real thing to be concerned about.

I like the idea of leaning on a decision like Jev model to identify such things.

aleph_minus_one 2 hours ago

> AI can help with that! Give an agent some rules, like via a skill for the project, and then point it at the PR/Issue for triage to determine if it's one that fits the rules for auto-closing (already reported and decided WONTFIX, for example). Have it run this across all your repos.

This requires a huge setup of the necessary AI infrastructure.

matkoniecz 3 hours ago

> My open source projects were barely sustainable when the few PRs that came in would fix actual, non-hypothetical, serious logic problems.

As a maintainer of some projects: at this point I would appreciate far more useful review of already submitted PRs.

As long it is not blind copy-pasting LLM output. That would be highly obnoxious attack.

chasd00 3 hours ago

rejecting a PR saying "i don't have the time to deal with this" is 100% valid thing to do. Don't let yourself be taken advantage of, it's your project. If the submitter doesn't like the answer then they an fork and go on their merry way, that's also a 100% valid thing to do and is the backbone of open source.

seki285 3 hours ago

Forking also doesn't mean completely going your own way! I have multiple repos forked where we and the maintainer disagreed on the direction, so I keep my additions on top of theirs in my own repo just how I like

larodi 3 hours ago

yeah sadly only 0.0001% of all users and reporters seem to understand this stand, which is oh-so-obvious if you have ever put anything public, but then people use opensource because it was hailed as free, more secure, and even more trustworthy. and as a result everyone and their dog not only seems to blindly prefer it but is then entitled to service which was never promised. what a massive cognitive dissonance indeed, but one that was carefully catered to and fed by the few key opinion leaders in the opensource sphere.

ravenstine 3 hours ago

PRs should be rejected by simply not enabling PRs in the first place. If PRs are needed for development, then that should be done in a private repo that is mirrored to a public one. I wouldn't even be surprised if that person'a readme says the project is open to contributions and that pull requests are welcome. I've found this contradiction to be very common, yet it seems like I'm in the minority for believing it's rude.

larodi 3 hours ago

and how does this get fixed? really - with more management is the only answer. who pays for this time - nobody. then they would blame the maintainer for being slow... and eventually fork if everyone's luck. why not close outright then?

athrowaway3z 3 hours ago

I've had my AI contribute to a bunch of open source so i'm on the other side of this.

For me they're real issues. Half of which i'd found before but never had the time to submit something for, the other half its things the AI will have encountered - and i check to confirm its a real issue.

The AI will follow guidance you leave in a repository. One of them said "no ai", so it reported that to me and I just forked and went on with my life.

There might be people farming for gh contribution i dontk now — but I can assure you the trend will continue, and afaict it is improving software; at least most of my contributions have been merged.

verst 3 hours ago

I don't accept PRs anymore for which there isn't an open issue where either maintainers discussed the issue or it has significant discussion among users. I'm trying to use issue labels to indicate if something is ready to accept PRs.

I see a lot of unsolicited PRs (and my case not from actual users but instead university students trying to pad their resume with random open source contributions but while clearly using AI exclusively)

saulpw 3 hours ago

Yeah, I just started auto-closing PRs from new contributors to avoid drive-bys. I want to know that someone actually uses VisiData before they are allowed to propose a change.

groundzeros2015 3 hours ago

Just disable PRs

no_time 3 hours ago

Consider taking donations. As a MIAB user, I love it and would be sad seeing it go away.

That being said, I know if one reaches that point in burnout, money won’t change anything. You are under no obligation to do any of this after all. So in the meantime, thank you. :)

merth 3 hours ago

Why not delegate PR approval to a group of trusted contributors? Give 10 people review and merge permissions, require at least two approvals and passing CI checks, and let them handle the day-to-day PRs. Surely distributing the maintenance workload is a better alternative to closing the repository to contributions?

dwoldrich 2 hours ago

Perhaps it is time for pull requests to come with payment in escrow that gets transferred after the maintainer does a review and approval.

This would eliminate a lot of AI slop, and I wish I had a popular repo so I could try it. I might unfilter and glance at the non-funded PR's once a year.

limagnolia 2 hours ago

Isn't that why it says "with the people who maintain it"? Like maybe open an issue or reach out and tell the maintainer, 'hey, I have this issue, and I want to fix it, would you like a PR if I do?' And then if there is interest, maybe a discussion about it as necessary.

This is what I do, and have done, since long before LLMs. And if they aren't interested? If its a big enough problem for me, I maintain my own fork. Forking is the greatest part about open source projects!

amiga386 2 hours ago

That's sad, but don't let yourself get burned out.

Free software and open source licensing, and projects like Debian, are set up so the software survives even the death of the author and the project. They can make their own improvements for their own ecosystem without upstream support. They integrate what comes from upstream whenever they can.

Someone getting their contributions accepted by upstream is a nice thing to have, but upstream don't have to accept it, and if they do, it's at their pace.

Secondly, don't let a pile of open issues and PRs bother you, unless they're fundamentally incorrect (in which case let your authorial voice be known). Because it's also useful for users of your software to give each other feedback and help each other out, e.g. "this app doesn't work with the latest macOS changes, but here's the code changes you'd need to fix it" means that users can help each other often for years before the maintainer gets around to looking at issues. If you're on some sort of code forge site, users can organise there. If you're not (and only accept patches by email or whatever), users can organise themselves elsewhere.

zahlman 2 hours ago

… What's your secret? I keep hearing from people on HN about how they're flooded by AI-driven PRs but my own projects get ignored completely. And most of the time that I check out some other random Show HN project, it's not getting much buzz either. For that matter, I commonly see stuff that has hundreds of seemingly organic stars, and flip over to the PRs and it seems pretty dead to me.

mceachen an hour ago

Perhaps add some guidance to your README.md or AGENTS.md, saying that you prefer concise issue reports with simple isolated reproduction sets over PRs? And that they must be, as you said, _actual, non-hypothetical_ issues?

And be OK with closing issues that have dubious merit?

jjsullivan5196 an hour ago

> I have a lot of people telling me what to do and it's exhausting

> Let me be the agent of a trove of people telling you what to do and how to do it

Do you see the problem here?

exe34 24 minutes ago

With the increasing power and lowering cost of LLMs, I wonder if we should move to a "apply these patches to the latest version for me" model. That way everybody is happy.

timbert 3 hours ago

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 play sound fonts? Cool, clone my project, instruct your LLM to add sound font support, and add support for your controller or your output device. Or convert it from Gnome to KDE.

The time and cost of doing this is so little now, why not? I'm getting more out of my computer than ever, and I'm happy about that :)

larodi 3 hours ago

readers here who have never tried this or does not understand what the person is talking bout - dare not speak. really, you have no idea, so please scroll further. those who understand will surely upvote. because _this_ is what savvy and pragmatic people (would and does) do in 2026 in order to get stuff done, perhaps they did otherwise back in 2012, but not anymore.

Conscat 3 hours ago

I think I principally agree with you, but did you need to write this in such a condescending manner?

augment_me 3 hours ago

This is a take that is outdated if not now, then in 3 months.

These has been this ladder of copium that "oh human still has input here for X, oh shoot it doesn't with Claude 4.5, well human is still needed for Y, oh shoot...".

You are suggesting that you can provide context that the model can't on its own. This is a search problem, every iteration it gets better.

We are at the stage in our company where "/goal optimize this" gets better result than any biased human context engineering can provide.

shmolyneaux 2 hours ago

I think it's reasonable that humans need to provide context for this, and situations like this, forever. The GP has a specific problem. The context of the problem exists in the real world, not something that the agent can search for. This isn't a "humans are still important" take. This is custom software for meeting the specific needs and preferences of an individual.

I fully agree with them that the easiest solution is to ask an agent for exactly what you want, and iterate from there. Evaluating and installing and learning off-the-shelf software is often more of a pain than doing it from scratch.

augment_me 2 hours ago

What prevents a solution where you physically hook up the needed components and then type "/goal make this keyboard extension work"

And the same library is built without the "seed" or baseline?

zahlman 2 hours ago

What does "work" mean? How should the agent know what UI you want? How should you know, until you try something out?

augment_me an hour ago

Answering here for both of your comments:

1) If the UX/UI is important for you, the agent can have access to your other work, or to your other conversation and build your tool with that in mind. This is just another search space question. If you have a documented, predictable taste, the models can efficiently produce what you need.

My uni supervisor/professor used to complain about my slop papers, then I started generating them in his writing style by just pulling down all of his papers and blogs, and he doesn't mind it now.

2) In general, the LLMs are great for steering opinion. There is good research on steering political opinion with LLMs. Your taste and opinions can be formed by the LLMs to like the solution that it provides you.

zahlman 2 hours ago

> You are suggesting that you can provide context that the model can't on its own. This is a search problem, every iteration it gets better.

How exactly do you propose that the model should search my thoughts? Of course I can provide context that the model doesn't have. I can provide context that does not exist anywhere on the Internet (unless I got hacked).

> We are at the stage in our company where "/goal optimize this" gets better result than any biased human context engineering can provide.

First, a "this" must exist to optimize. Second, you have to be happy enough with it that optimization is the only problem.

montenegrohugo 3 hours ago

Fully aligned, i echo the above experience strongly.

However, it seems to me like there must be some middle ground, between sharing architecture "ideas" and full on code PRs.

I myself maintain various FOSS projects; and incoming PRs are marginally useful. generally i just close, and copy with claude following my own & project taste (crediting initial contributor).

nayroclade 3 hours ago

Yes, right now this is absolutely the best way to build bespoke software, but it is also very wasteful. Think of all the time and the billions of tokens being burned to repeatedly reimplement apps and features. LLMS code fast, but not yet instantaneously or perfectly for complex features.

What we need is more than just OSS templates. We need fully LLM-managed "software libraries". These would be like package managers on steroids. They would be a huge hierarchy of LLM-coded modules. When you ask for an app, your LLM assembles it from the modules that already exist. If you ask for a novel feature, it codes it up and places it into the library.

So, for your VST player example. You would ask for a barebones version with just the features you need, and your LLM would assemble it for you from preexisting library modules. Then you ask for sound font support. If there is an existing sound font module, it would download it and add it into your app. If there wasn't, it would create one and put it into the library, so the next time someone asks, they can quickly get a VST player with sound font support.

jhloa2 3 hours ago

I have a similar experience where I’ve been learning the keyboard but didn’t like the available free options and the good paid apps had really expensive subscription plans so I had Claude build me something that runs natively on my iPad, with midi and microphone support and generates custom learning plans for midi pieces that I import.

I’m an engineer but not a software engineer and it’s been pretty interesting trying out vibe coding and seeing the barriers of entry being blown apart.

I’ve been progressing at learning the piano quite a lot faster than I expected with this. I’ve been debating open sourcing it but I’m not sure I want to take on the work of managing it

compacct27 24 minutes ago

Oh wow, just did the exact same thing on my end. If I’m struggling with some fundamentals I’ll just have Claude scour the internet for the best instruction and throw it into a lesson

red_admiral 2 hours ago

This would work if all LLM contributions were not only open-source, but also public domain or something. Otherwise you'll get a mess of incompatible licences.

ValdikSS 3 hours ago

>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.

I've seen this idea: https://v-it.org/

timbert 2 hours ago

Thanks for sharing this link! It's a great idea, maybe I'll contribute as well :)

rabf an hour ago

I think supplying the solid base on which to build along with instructions for a users LLM is very valuable just now.

pitchlatte 43 minutes ago

as someone who’s been working with MIDI for a hot minute, I’m really puzzled by your experience. either you have a very fussy controller or you received bad advice. most samplers like Kontakt and modellers like OrganTeq (very well regarded organ modeller) literally comes with a standalone version so that you don’t need to fire up a VST engine/DAW.

rewgs 25 minutes ago

> 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.

Hate to say it but this is genuinely just a skill issue.

Resorting to building a DAW tailored to your own lack of understanding because you can't be bothered to learn tools that are extremely widely used and well-documented is the most extreme case of yak-shaving I've ever seen.

IncreasePosts 3 minutes ago

OP got what they wanted in 3 hours.

Since this is a skills issue, could OP have learned everything they were lacking and got a more standard set up working in 3 hours?

Isn't needing to know how to manage and coordinate various software packages more yak shaving than just telling AI what you want to do? OP wanted to play piano and hear it on their computer with some effects, and that's what they got

linsomniac 3 hours ago

> 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 "vibe coded" alternative (mostly enhancements and fixes for other users use cases). I'm pretty confident that this wouldn't have been something the apt-cacher-ng or apt-cacher maintainers would have been interested in accepting.

delichon 3 hours ago

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.

rckclmbr 3 hours ago

Yep similar experience. I essentially have a database that my agents connect to, and it insert/update/delete rows. No app or even api required

ValdikSS 3 hours ago

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/

ValdikSS 11 minutes ago

I also wrote a lengthy post a while ago, read only if you're really interested in this topic, otherwise spend your time for something more important.

https://news.ycombinator.com/item?id=47988108

PaulKeeble a minute ago

We have really needed something like this for years. I have repeatedly run into the issue where a project doesn't take any form of patch for a bug or feature I need and its often really unclear which type of project it is. I started about 10 years ago looking at the pull requests and issues and seeing if they ever merged changes and most projects don't. It was a strong signal not to even try.

Now with AI there is a deluge of fixes but its also always been the situation in open source that most projects are closed to contributions.

poisonborz 3 hours ago

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 4 hours ago

I agree but open source needs to solve the monetization problem; developers need to eat.

jarym 4 hours ago

I reckon we’re going to see more proprietary software over the next year.

Gone are the days of commercial organisations using OSS as a marketing tactic to gain a base they later monetise. It worked, it was a tactic and no one really liked it.

Your options will be:

a) community led OSS - like Apache projects, CNCF projects, etc

b) some dudes weekend OSS project

c) commercial vendor, likely proprietary or at best ‘source available’

txdv 3 hours ago

some dude coding with 5 max claude accounts gets very far these days

__MatrixMan__ 3 hours ago

I disagree. My agents are godlike when I ask them to operate software whose previous version's source is in their training data, and pretty confused when I ask them to operate something proprietary. I wouldn't even use proprietary software if the vendor was paying me to do so (unless they were paying me quite a lot) because there's just so much extra friction around it.

The ideal future of software is not as a product or a service but merely as a tool, used by people with a problem to solve that has nothing to do with selling the tool.

everforward 3 hours ago

I reckon we’ll see the opposite.

This is the first time “open source” has meant anything other than “probably free” to the average person.

I constantly hear people complain about UIs. You know who probably makes a great UI for non-technical retirees? A non-technical retiree. They’ll probably start from forking an OSS project, though.

I think the really clever folks will move up to building vim/emacs/Firefox esque apps that are heavily scriptable, and your weekend OSS projects will be done by non-technical folks who just want something really specific.

bsder 3 hours ago

> I constantly hear people complain about UIs. You know who probably makes a great UI for non-technical retirees? A non-technical retiree. They’ll probably start from forking an OSS project, though.

You know what makes a great UI for non-technical people? Codex or Claude.

GUIs were a response to the limited resources available on old computers. And, as we're increasingly finding out, text is FINE. People like Teh Pretty(tm), but they'll take plain text if it solves their problem.

But, congratulations, you DID identify the primary bottleneck--customer support. And, no, I am NOT going to be unpaid customer support for non-technical people. Bleah! Get back to me when Claude/Codex don't suck for that.

pwndByDeath 4 hours ago

I work a job for my money that isn't developing and haven't yet developed something worth enough to others to consider making money that way. If I did, I would consider a finite sum (e.g. kickstart) then release the code. I see software/digital goods as only scarce until they are released. So their value plummets to $0, its only nature defying legal structures that make it otherwise.

Ampersander 4 hours ago

More like developers want to buy expensive cars and a second home. Software pay is GOOD.

phito 4 hours ago

Absolutely not the case everywhere.

matkoniecz 3 hours ago

For typical work on FOSS projects?

Even if you limit it to FOSS projects extensively used by massive corporations i is far from rosy.

komali2 4 hours ago

I don't think of open source software as a way for me to make money, I think of it as a way for me to prevent other people from making money.

An open source project management software nips at JIRA's profit margins. OSM loosens google maps' stranglehold. The swath of FOSS crms delegitimizes Salesforce's per-seat cost. Most recent example is open weight LLMs driving a spike of fear deep into the heart of the current lynchpin of the American economy.

MIT license was a mistake. We tried to play by the rules of capitalists and the obvious happened: the capitalists exploited us. "Thanks for the free labor! By the way, we don't hire people that don't have FOSS commits on their resume." Google and Facebook, last I checked, forbid the inclusion of GPL3 code in their projects. Great! Let's make more GPL3 copies of their software so nobody has to give them money anymore.

Shiggy_ 3 hours ago

The marxist larping is cringe. In my experience, people that are like this likely have 0 commits to actual OSS.

OSS is a great passion project for a developer that wants to take it on, and when the community comes together, they can do incredible things. From a social perspective, I'd struggle to find anything that's more empowering to the average person than the ability to spin up a Linux server and get going in like 30 minutes.

But support is lacking. Proper documentation can be lacking. The sheer amount of work required to host, fix, update, and keep uptime up on real software at a real business is beyond a hobby, and enterprise support is mandatory, not optional. There are legitimate legal requirements that need to be met.

The fact of the matter is that the nature of the capitalist system that exists in the western nations is the same system that allows for OSS to exist at all. Tailscale was hard as hell to develop. Docker was hard to develop. I love the opensource alternatives to these services. I wouldn't use them at my company.

ValdikSS 3 hours ago

>I think of it as a way for me to prevent other people from making money

That's a very common misconception I see among the developers. They get upset when someone sells their software, especially when the author distribute it for free.

Please read this: https://www.gnu.org/philosophy/selling.html

If the license doesn't allow to sell free software, the license is not free.

If you don't want others to sell your software, you need to use non-free license. There's absolutely no shame for that.

zahlman an hour ago

> That's a very common misconception I see among the developers. They get upset when someone sells their software, especially when the author distribute it for free.

No, that isn't the argument here at all. The argument is that the existence of OSS alternatives (for which there is no real reason to pay more than a nominal distribution fee, aside from contracted support) makes it harder for proprietary software to retain commercial value.

ValdikSS an hour ago

>for which there is no real reason to pay more than a nominal distribution fee, aside from contracted support

FOSS doesn't mean you have to distribute the software for free. If you want to earn money from FOSS, just don't publish it and sell it instead. It doesn't make it less open.

I sell open-source software of myself and others, for example, quite successfully.

Linked article states:

>So if you are redistributing copies of free software, you might as well charge a substantial fee and make some money. Distributing free software is an opportunity to raise funds for development. Don't waste it!

It has been this way all these years, that's why I call it a common misconception. The GNU article by the link above is from 2012 or earlier.

imtringued 2 hours ago

If you thought this through until its final conclusion then you would notice that open source developers would simultaneously be paid more money than proprietary company developers and charge less money than proprietary companies.

People would gladly pay you more because it means they have to pay less.

The only necessary requirement is that the payment goes down with the number of payers and that there is no free rider problem.

sfink an hour ago

I mostly agree, but I don't think that's quite it either. For me, OSS is neither a way for me to make money, nor a way to prevent other people from making money. The latter is closer, but it's not other people making money off of what I create that bothers me, it's that users have to pay someone else in order to use what I created.

I think of OSS as a way to get value into the hands of users and for them to not have to pay someone else for it. I honestly wouldn't be too bothered if they had to pay me, but I relinquish that payment because not paying me means more users and more use, and I have the privilege of a decently paying tech job, so for my personal cost/benefit analysis the free software wins. (And yes, I default to GPL not MIT/BSD.) And it's not just the direct users of my software that I care about, it's also the overall ecosystem of freely available and modifiable software that I want to contribute to.

It also doesn't bother me when other people use OSS as an anti-competition mechanism. That's a different reason to do something that happens to resemble what I'm doing. It doesn't contradict or interfere with what I'm doing nor my reasons for doing it.

II2II 4 hours ago

Irony: the number of developers who rely upon other people's open source to develop commercial software or services.

Once upon a time, people payed hundreds or thousands of dollars to acquire software development tools. Even those who programmed as a hobby would have to spend a fair bit of money if they wanted to grow beyond interpreted BASIC.

I'm not claiming the current situation is ideal, but open source has given us much more freedom to program.

criddell 3 hours ago

For maintainers who are being flooded with low-value PRs, maybe they should put up a PR paywall.

PR coming from an individual? Make the price low but not zero and experiment with the price until the PR rate is manageable.

PR coming from a company? Charge your regular rate.

__MatrixMan__ an hour ago

I'd be more likely to participate in something like that if instead of collecting the money, the maintainer is just requiring that I donate it to the EFF or something like that.

Money as proof of this-guy-actually-cares isn't an awful idea but you gotta be careful to not become a parasite.

ValdikSS 3 hours ago

Many open-source projects are made for the author's needs, and the author is not interested in implementing feature requests they don't need.

Sending no-strings-attached donations to the person instead of targeted fundraising of the project is just a disservice if you're expecting maintenance, more harm than good.

shmolyneaux 2 hours ago

> 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.

dataminded 38 minutes ago

No. The old way, where you compromised your workflow because a company, indie dev or maintainer had their own preferences, is dead or dying. Models are now good enough that you can have exactly what you want for little or no extra cost. Most importantly, we don’t have to go through gatekeepers anymore. (OSS maintainers are gatekeepers too: nice, underpaid and overworked, but still gatekeepers.)

My apps are native and fast. They run on all my devices, connect to each other through APIs and MCPs, and look the way I want them to.

cheney_2004 4 hours ago

Whats wrong with the term vibe coding? If it has a negative connotation, the problem isn't the choice of words, the problem is the software being produced. Rather than change the name, try and figure out how to raise the bar.

fork-bomber 4 hours ago

I personally think that there's nothing wrong with vibe coding so long as there are as close to watertight ways, checks and balances to verify that the output is correct. And the best way to do that is to invest domain specific expertise in coming up with as comprehensive a test schema as possible.

If the test schema passes and if your original articulation of intent was correct, then what you have is already very good. From that point onwards, it's the question of accelerating development by just reviewing the output of the LLM and getting it into the right shape.

The combination of the review of the output of the LLM and the review of the test schema and its output, that is going to be a lot quicker to do than coding everything from scratch with a proper design paradigm.

pietervdvn 3 hours ago

> the best way to do that is to invest domain specific expertise

And precisely that is the issue: people vibe coding something and releasing it to the world don't have this domain specific knowledge to build upon. It used to be that building the software would force the programmer to learn about the domain, but that link is broken now too.

fork-bomber 3 hours ago

I don't disagree. My point is that for the domain experts, it is undeniable that Vibe Coding is a massive accelerator.

zahlman an hour ago

> … so long as there are as close to watertight ways, checks and balances to verify that the output is correct.

… so, as long as it isn't actually "vibe" coding?

fork-bomber an hour ago

Domain experts can also do vibe coding is the principal thesis of what I'm trying to say.

So there's vibe coding for the general populace, and there's vibe coding which domain experts can use to articulate problem statements in well-formed ways and articulate test schemes to ensure that their articulation of the problem is actually solved in the best way possible.

Hopefully that makes sense.

Industry happens because of domain experts for the large part.

If domain experts have a way to accelerate their wherewithal significantly, then industry progresses significantly.

The promise of LLMs and the promise of vibe coding is fundamentally that domain experts of industry can significantly accelerate progress.

The rest, who are not domain experts and who are not of the industry, are also progressing, but the value of the progress they have in terms of how they contribute to how industry contributes to society is fundamentally questionable.

jmyeet 4 hours ago

Vibecoding has come to mean "AI slop code" where the people producing it don't understand it, like at all. It can be poorly structured and hard to comprehend.

I believe that train has sailed on this association.

rectang 3 hours ago

The word “vibe” vividly conveys that, whatever its merits, the process of “vibe coding” is not rigorous.

zahlman an hour ago

What do you mean "come to mean"? At what point did it mean anything else, and why would it have?

mtswish 3 hours ago

The term was defined to mean slop. If you are vibe coding you are not doing engineering. I assume most customers don't like hearing that the people working on their code aren't aware in any way of the code they are pushing.

NooneAtAll5 3 hours ago

> I assume most customers don't like hearing that the people working on their code aren't aware in any way of the code they are pushing.

why is it bad that customers hear the truth?

listenfaster 2 hours ago

I feel like AI has removed bottlenecks to me being able to contribute to open source projects, and the author is spot on with the “don’t be a jerk about it “guidelines”. Understanding the social element, the community function around maintenance of a project is a different ball game every time, and for me has often been its own research project. I remember before AI killing hours figuring out where to start in understanding mame, csound, and other older projects that have had many many different contributors, and weren’t the most welcoming to newbs. Now I have an assistant to ride shotgun with me while I figure out where to contribute, and can focus on whether my contribution is useful. I have this picture of a world of small functioning tribes suddenly being inundated by nomads who wanna join up.

Ersho an hour ago

Recently I see even mobile apps that are just LLM wrappers (or not even) charging 5 - 20$ for premium versions and can be one shot with claude or codex. For example, like you mentioned habit tracking, gym tracking, pdf reader, scanners, language learning and so on.

Also, its hard for me to trust their AIs and feed again and again my information to many different apps and their AIs.

If you think about it, you need one claude or codex subscription and you can generate your own apps with your own AI models that I trust more than ones used in the apps.

Recently I started working on open source local app playstore. Would appreciate your feedback and any input - (https://github.com/Ersho/sayn)

Kuyawa an hour ago

I just told DeepSeek to write a running app customized to my own needs (like Strava), and presto I now have a nice app for my running sessions with just the info I want, no ads, no subscriptions, a full map (openstreetmap) of the route, charts, stats, widgets about time, pace, steps, heart rate, calories, elevation, all I need in my own app, just for me (and my wife)

You may not need it, may not like the colors, the UI, the depth, features, etc. That's the beauty of AI it can build whatever you want however you want it, all for less than a dollar in less than an hour

Yes, we need more apps, tailored to every user. From now on I refuse to install any app not customized to my needs

And yes, we should share more, so AI learns from all of us and builds stuff for us with all the shared knowledge of all

philipwhiuk 25 minutes ago

> Yes, we need more apps, tailored to every user. From now on I refuse to install any app not customized to my needs

> And yes, we should share more, so AI learns from all of us and builds stuff for us with all the shared knowledge of all

But the output of this is that every running forum is deluged with hundreds of vibe-coded apps that are marginally different from each other - a moderation burden.

kaishin 2 hours ago

I build my own apps in order to solve real world problems I have. I don't see myself opening random PRs in OSS repositories only to get most of them rejected or ignored.

cush 3 hours ago

We probably need more apps with fewer features and more bespoke apps for specific domains rather than having businesses cobble together a dozen SaaS offerings.

jstanley 3 hours ago

Typically open source projects will not thank you for your contribution and will instead be annoyed with you for bothering them.

Yes fix bugs and add features etc. for your own personal use, but don't get your hopes up about contributing back, it's usually a waste of time.

_nobody 3 hours ago

We need more apps. Specifically, everyone should have complete ownership over their own software, so either people learn to build it themselves or truly own the tools they use, instead of renting it via subscriptions or losing control over it by the whims and fancies of c-suites, who brick the software which we paid for.

jph 3 hours ago

Better open source can leverage better ways to learn and contribute IMHO. I'm working on building blocks for open source projects, using comprehensive code annotations to help developers learn, experiment, fix, and remix. I welcome help, advice, criticism.

1. Friendly editor: Vix @ https://github.com/vixide

2. Broader web UI: Lily @ http://github.com/lilydesignsystem

3. Smarter web service helpers: Axa @ https://github.com/publicprojects-io/axa

I tried many open source software projects before starting these, and I'm a longtime open source developer so I highly value all the work from people working on vi and emacs, Daisy UI and shadcn, Rocket and Loco, and more. These projects are all aiming for public nonprofit social good.

listenfaster 2 hours ago

These look really cool and are thought-provoking for me, as I was considering starting a friendly editor and a design system myself ha. You should show HN these.

coretx 3 hours ago

We need less apps with over 9000 functions and more that do just one thing right.

maxdo 3 hours ago

Alternative view : for security reasons open source use will shirnk, since it's becoming most dangerous vector of attack.

Future Software Factories will have extra large static harness, that will be have a very few dependencies, e.g, reactjs, bundled into the package. Even nodejs probably will be more of a runtime feature, patched by the cloud.

open source was mostly a feature of not enough software eng resources. Now , since this is in abundance, instead of a shortcut it becomes a risk.

ValdikSS 3 hours ago

>patched by the cloud

Yes, something like that.

I've pitched the idea on twitter and asked security guys whether someone does something like this:

Say we have 0/1-days in Python 2, which is not maintained. I'm thinking of software + service which will:

    - Detect the exploit attempt
    - RE and dissect it
    - Document it, propose fix
    - Publish it somewhere (!)
    - Others discover it (!)
    - Individual agents apply the fix locally
This way we don't need centralized maintenance, although it will work better with it.

jayd16 2 hours ago

So in this future, we don't use hardened software. We use security through obscurity.

...But also in this future, the source code of all of these programs is stored in context in the cloud of a few tech companies with unknown levels of security around such context?

Considering they likely use the stuff for training, what are the odds its actually air tight for the foreseeable future? The odds are 100% that the contexts will be compromised because that's the conjecture with the open source projects as well, yes?

Doesn't that seem concerning?

maxdo 3 minutes ago

if the models keep getting that better, security, bug fixes, will be part of the model/harness methodology. not scary but depressing.

For training they can / already rely more on RL, but even for code samples , it's more vetoed, rather than a random library that ports another open source library in python and it's proudly open source.

gortok 2 hours ago

If a project ever has a hope of being sold (“Licensed”) commercially, open source is a death knell. In part due to the AI “training”, and in part due to how easy it is for larger actors in the space simply to take the code and do whatever they want with it.

The problem with Open source presently is that it provides no way to sustain the energy used to support it. I have a limited amount of time in my life; I currently spend roughly 1/3rd of it supporting my family. If I use another chunk of time to ‘support’ open source, I’m looking at my work being taken and used for the profit of others without being able to profit from it myself. If I can’t profit from it, I can’t use it as leverage to make it so I don’t need to spend 1/3rd+ of my life working to support my family.

I am currently writing software with the expectation to sell it. I may even give away copies of it, I haven’t decided yet, but the source code won’t be online, and the support documentation will be behind a registration wall, as will the API. Nothing will be visible on the public internet, not for any other reason than AI scrapers and the large companies that use them.

There may be other ways for small software businesses to be sustainable, but at this moment it’s hard to see them.

Ericson2314 4 hours ago

That's why I work on Nix. Let's make everything easy to install everywhere.

FinnLobsien 4 hours ago

I agree that this would be a great thing.

But I don't think there's a big overlap between the people who could even name one open-source library and the people flooding the market with vibe-coded to-do list apps.

meerita 2 hours ago

That's not possible. Somethimes, the open source projects take a path you don't want and they don't want. So you have to build yourself the version you want.

florieger 4 hours ago

https://jordankrueger.com/images/gallery/blog-better-open-so... Error: „Load cannot follow more than 20 redirections“

pandemicsoul 3 hours ago

Hmm, just tried it and it worked for me?