I've come for my daily dose of corporate wolf in sheep's clothing marketing. Was not upset.
Linux
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
My prophecy is that open source world is going to have three kinds of projects:
-
Projects that use LLM
-
Projects that bite the dust
-
Amazing artisan art projects that are absolutely beautiful but ultimately not very significant
Buddy a project to be successful doesn't need to a lot of users and fornsure doesn't need LLM
lookit nostradumass here
-projects that work
- projects that die from slop
- zombie projects held up by slopmongers
I gotta admit KDE’s stance on this frustrates me a lot.
On the flip side… I am also fully aware that policies of prohibition, in the broadest sense, tend to not be terribly successful, and I wouldn’t be shocked if some contributors simply excise the “co-authored by ” from the commit messages with a simple pre-push hook or something like that on projects that explicitly prohibit LLM/codegen usage.
IMO one of the major problems with LLm code generation is that it has the capacity to overwhelm human capacity to review code and properly understand the codebase.
From that perspective, a prohibitive policy doesn't have to be 100% effective to be useful, it just needs to slow things down enough to keep the manageable and maintainable (and fun to work on).
i think the copyright question is still unanswered: it could turn out that any LLM-generated code is a copyright violation by definition unless trained exclusively on a clean, legitimately-obtained dataset (which few of the major models are).
Will projects that allow LLM contributions have to roll back years of progress when the other shoe finally drops? Seems like a huge risk, especially for FOSS and copyleft. I think disallowing LLM-written contributions until this is all sorted out in the courts is the pragmatic move from a legal perspective.