Being Against LLMs Is Against the Spirit of Floss

WCSTombs

This article makes some reasonable points but a lot of bad ones, and ultimately even the "good" ones don't really support its conclusion. > But rejecting code not for technical reasons (of which there are often many for vibecoded code) but for ideological reasons is unfortunate. [...] Such a policy — that contributing to a project because of the circumstances of the contribution’s creation, and not due to its quality — is directly contradictory to the spirit of free software. Okay, what is FLOSS? Software published under free and open-source licenses. It's literally the definition of the concept, and thus a FLOSS project cannot accept contributions for which such licensing is impossible, regardless of technical quality. For example, a FLOSS project can't accept code copied out of a nonfree project, or copied from a project with an incompatible license. The provenance of the code has always been central to the whole endeavor. When LLMs enter the picture, there are at least two problems. 1) LLMs were trained largely on copyrighted works, and it's unclear if the models themselves or their outputs should be considered to be derivative of their training data. 2) It's possible that LLM outputs can't be copyrighted at all, not as FLOSS or under any other license. I won't try to get into the many arguments and opinions on both sides regarding those issues, but suffice to say they're contentious enough that, regardless of where an individual maintainer's opinion may fall, IMO it's definitely not wrong to refuse to accept LLM-generated code just to avoid needing to resolve them. The "spirit of FLOSS" was never primarily about the technical quality of code, but about the freedom to use, study, modify, and redistribute software, although technical quality also benefits in some ways from the FLOSS ethos. I actually do care deeply about technical quality as well, so I have to mention that many of us have serious doubts about the overall effects of LLMs on software quality in the long term. Even if individual maintainers can maintain high standards for their projects, IMO promoting LLMs still creates long-term downward pressure on software quality that comes back to harm everyone.

cyanydeez

local models, yes. Cloud models, no.

GPerson

“Arguments that llms fundamentally a part of a system of political oppression fall flat against the case of open-weight models that can be run at home on (high-end) consumer hardware.” Can anybody comment on the validity of this in 2026? Compared to Fable on a $200 monthly subscription, what is a $2400 investment in a home setup (including electricity) getting me in a year?

moomin

The elephant in the room here is that there are no FLOSS LLMs. Renders most of the rest of this argument moot.

ButlerianJihad

It seems undeniable that LLM "vibe coding" presents an existential threat to F/OSS, its legal underpinnings, and its ethos. Richard Stallman's vision involved an exploitation of copyright to ensure that software would become free and remain free, and get even freer as we went along. The GPL and its derivatives have been, for decades, a really potent weapon to wield against closed-source, corporate interests, and proprietary software. Especially in the form of GNU/Linux: the kernel and its major distros are ultimate bastions of GPL software. Creative Commons relies on copyright to work. BSD, MIT, Apache, all the F/OSS source licenses, and permissive licenses: they all rely on copyright. So how are LLMs going to help here? If LLM output remains uncopyrightable, then we're in trouble. It seems that only a minority of jurisdictions confer any rights to the "prompters" or "vibe coders" of genAI works. If any given contributor to an F/OSS project cannot own, copyright, or assign rights from their works, then the project cannot remain "free". Oh, sure, any F/OSS can become public domain, and purely public domain works are indeed "free software" but they can't be GPL'd and they can't be subject to any additional "freedoms" such as requiring attributions. Public domain software can be subsumed into trade secrets and closed-source projects. What company will want to contribute public domain code to any public project that they've written with LLMs... they will simply go closed-source. I think any F/OSS dev should be concerned, at this point, with LLM contamination of code bases. Many projects are wisely clamming up and prohibiting AI-generated code, to the extent possible, but that's sort of impossible, isn't it? Contributors will simply claim ownership and claim manual output, when it wasn't, and who will prove them wrong?