Afaik LLM-generated code cannot be copyrighted in the USA, and therefore cannot be licensed. It's automatically public domain. This makes it incompatible with most OSS licenses. Several of my personal favorite projects have already prohibited LLM-generated code. That doesn't mean the frequency and quality of contributions won't still increase. I use my LLM harness for all kinds of grunt work that would have sucked up hours. Git surgery, code exploration, PM. But we don't need a whole new paradigm for a brave new world. I've heard that'd boil the sky and poison the water anyway. Too expensive.
The context around copyright of LLM code, at least in the US, is currently more complicated than clear. See for example [0] and the comments on the article it's responding to.
Hasn’t this always been the case with forks?
I'm carrying so many patches these days. I need a term for it. This feels like an ok go at it, a remix.
Mentioned this just the other day, the want for a term for this:
> mercy it's not even a fork. we don't even have a word for this! i'm juggling a bunch of patches atop opencode. sort of a fork. a running fork? https://bsky.app/profile/jauntywunderkind.bsky.social/post/3...
Afaik LLM-generated code cannot be copyrighted in the USA, and therefore cannot be licensed. It's automatically public domain. This makes it incompatible with most OSS licenses. Several of my personal favorite projects have already prohibited LLM-generated code. That doesn't mean the frequency and quality of contributions won't still increase. I use my LLM harness for all kinds of grunt work that would have sucked up hours. Git surgery, code exploration, PM. But we don't need a whole new paradigm for a brave new world. I've heard that'd boil the sky and poison the water anyway. Too expensive.
The context around copyright of LLM code, at least in the US, is currently more complicated than clear. See for example [0] and the comments on the article it's responding to.
[0]https://news.ycombinator.com/item?id=49354482