The use of large language models (“LLMs”) has exploded in recent years, including in the generation of source code. But even as their usage gains popularit...
Why would we want to license vibecoded slop code built with a system that is (in most cases) probably and admittedly actively using data from sources with incompatible licences or no licences at all.
probably and admittedly actively using data from sources with incompatible licences or no licences at all
You answered your own question. I don’t know what you try to say, but the article and our discussion is explaining if and why licensing code that is vibe coded is possible or makes sense at all. And you point the problem out that this is problematic and probably not possible in good faith. So its not about what we want, but about if and what is possible.
Right but why would we want to license vibecoded slop?
Irrelevant question. For licensing and copyright questions, quality of code is not important.
See Microsoft and Google.
Why would we want to license
vibecoded slopcode built with a system that is (in most cases) probably and admittedly actively using data from sources with incompatible licences or no licences at all.You answered your own question. I don’t know what you try to say, but the article and our discussion is explaining if and why licensing code that is vibe coded is possible or makes sense at all. And you point the problem out that this is problematic and probably not possible in good faith. So its not about what we want, but about if and what is possible.
Indeed, though I was just rephrasing the question from the person you were replying to.
Responded to the wrong comment, apologies.