6 ms·
That's the way it's always worked. You read books to learn to code, then write code and you get paid for it, but that money doesn't trickle down to the writers
by vasdae 3y ago
That's the way it's always worked. You read books to learn to code, then write code and you get paid for it, but that money doesn't trickle down to the writers of the books that taught you to code.
- freejazz 3y agoThose books you read were copyrighted.
- vasdae 3y agoDespite the books being copyrighted that doesn't give the authors any rights over the code I have written.
- anotherhue 3y agoIt does when you produce the code verbatim, as happens frequently.
- jnovek 3y agoBetcha I’ve spontaneously produced code that’s been written before. Who do I owe royalties to?
- sensanaty 3y agoYou're not a computer whose sole purpose is to regurgitate code verbatim at massive scale when requested, unlike an LLM designed for exactly that purpose.
- andromeduck 3y agoExcept LLMs aren't exactly optimized for verbatim regurgitation.
- mistrial9 3y agounder what system of law?! -- there are at least four major economies in the world, and they all have different rules about these intermingled issues.
- imoverclocked 3y agoExcept, the “books” in this case is the code/content that people might like to get paid for in the first place. Also, AI companies aren’t “buying the books”
- FrenchDevRemote 3y agoyou're not buying books when going to a library
- LoganDark 3y agoThere truly is an xkcd for everything: https://xkcd.com/294 https://xkcd.com/294
- lelanthran 3y agoWell then let Microsoft send their employees with a camera each to the library.
- spaceguillotine 3y agoyou joke but Google did exactly that, i worked on the program for a little while.
- sensanaty 3y agoThe library pays/paid for those books (usually at much greater cost exactly because they're meant to be accessible), most often through taxes.