51–60 of 65 posts
How many others are now reluctant to open source their code because they don't want it to end up in the training for an LLM? I certainly am.
Things change. The barrier to entry decreased, meaning more things will get created, more people will participate in communal efforts, and quality will depend on AI capabilities and figuring out how to curate well - better tools, less friction between idea and reality, and things get better for everyone. Just because some things suck, for now , doesn't mean open source is being killed. It means software development i…
Further to this, the quality problem is affecting the entire industry, not just FOSS. Anyone working on a large enough team has already seen some contributors pushing slop. And while banning AI outright is certainly an option at a private company, it also feels like throwing out the baby with the bath water. So we’re all searching for a solution together, I think. There was a time (decades ago) when projects didn’t n…
Earlier quoted context omitted.
What's not the same is that the LLMs used to create the code are highly centralized and controlled. I suspect it's only a matter of time until the content industries start trying to restrict what code LLMs are allowed to produce so that you can't use an LLM to bypass DRM.
> I suspect it's only a matter of time until the content industries start trying to restrict what code LLMs are allowed to produce so that you can't use an LLM to bypass DRM. I don't think this is a possibility anymore for multiple reasons. As others have already pointed out there are already "open models" available to use and that genie can't be put back in the bottle, restricting the commercial models wouldn't fix…
Earlier quoted context omitted.
> no longer any need to use a library at all As someone who works on medical device software, I see this as a huge plus (maybe a con for FOSS specifically, but a net win overall). I'm a big proponent of the go-ism "A little copying is better than a little dependency". Maybe we need a new proverb "A little generated code is better than a little dependency". Fewer dependencies = smaller cyberseucity burden, smaller reg…
> probably 90%+ of npm packages could probably go I feel npm gets held to an unreasonable standard. The fact is tons of beginners across the world publish packages to it. Some projects publish lots of packages to it that only make sense for those projects but are public anyway then you have the bulwark pa lager that most orgs use. It is unfair to me that it’s always held as the “problematic registry”. When you have a…
Earlier quoted context omitted.
There are competent open source LLMs out today. They are not highly centralized.
There's one at the top of Hacker News right now, Qwen3-Coder-Next: https://news.ycombinator.com/item?id=46872706
Things change. The barrier to entry decreased, meaning more things will get created, more people will participate in communal efforts, and quality will depend on AI capabilities and figuring out how to curate well - better tools, less friction between idea and reality, and things get better for everyone. Just because some things suck, for now , doesn't mean open source is being killed. It means software development i…
I think you have it backwards. Barrier to entry just went up, why would I use a library when I can ask LLM to make one for me. It shifts in a way where „left-pad” kind of thing will not happen because no one will need that kind of „library” because LLM will generate it. I see it as a positive thing, no single schmuck will be terrorizing whole ecosystem when there will be dozens of of different LLMs that can write suc…
I don't know how many times it's been said, but writing the code was never the hard part.
People who depend on LLMs are making the same old naive mistake that's been around for decades.
It's actually worse than in the past! At least the stubborn people who would insist on writing everything themselves had to comprehend their own code and were projecting overconfidence to mask their attempts at learning. We would turn a blind eye to junior devs doing this, but then reject it in code review and tell them to just use the correct library. Now we still have all that arrogance, but without any of the effort to learn jack shit.
I used to think open source was something I'd focus on when I retired. Instead I'm doing it now. I built Clippy (https://github.com/neilberkman/clippy) from scratch, a much better bcopy, that fixes a real gap in pbcopy, and it hit 200 stars and Homebrew core in seven months. Neither of these would exist without AI assisted development. My DocuSign Elixir SDK sat basically unchanged from 2021 to 2025, other than a few external contributions. I knew it needed a full migration of the OpenAI code gen layer, LiveBook examples and a million other tweaks. With coding agents I implemented everything useful I could imagine.
Am I the only one? There must be other devs out there resurrecting stale projects or shipping tools they never had time for.
Earlier quoted context omitted.
Further to this, the quality problem is affecting the entire industry, not just FOSS. Anyone working on a large enough team has already seen some contributors pushing slop. And while banning AI outright is certainly an option at a private company, it also feels like throwing out the baby with the bath water. So we’re all searching for a solution together, I think. There was a time (decades ago) when projects didn’t n…
Projects back then did not use pull requests because that is a concept created by GitHub.
FOSS projects didn’t always have a standard process for Fagan inspections.
Things change. The barrier to entry decreased, meaning more things will get created, more people will participate in communal efforts, and quality will depend on AI capabilities and figuring out how to curate well - better tools, less friction between idea and reality, and things get better for everyone. Just because some things suck, for now , doesn't mean open source is being killed. It means software development i…
AI won't teach collaboration.
Open source is a lot more about learning the norms of working together than the actual underlying software.
Earlier quoted context omitted.
Further to this, the quality problem is affecting the entire industry, not just FOSS. Anyone working on a large enough team has already seen some contributors pushing slop. And while banning AI outright is certainly an option at a private company, it also feels like throwing out the baby with the bath water. So we’re all searching for a solution together, I think. There was a time (decades ago) when projects didn’t n…
Projects back then did not use pull requests because that is a concept created by GitHub.
the concept is at least as old as git itself, possibly even older. github just created a webinterface for it.