Live data from Hacker News

Is GitHub Copilot a blessing, or a curse?

fast.ai

171–180 of 201 posts

Re: Is GitHub Copilot a blessing, or a curse?

#171

Copilot was made from stealing code on Github, ignoring the licenses set on repos such as e.g GPLv2, using AI as a trick to license-launder code. Copilot has announced their plans to become a paid service. So this product that would not be possible without public, open-source code will itself be non-public, closed-source, closed-data. It is extracting value from the commons and funneling it to a private company.

The following is just my opinion, and I'm not that hard-set in case anyone has any nice arguments. Generally, when you (for example) use GANs to learn from (copyrighted) images and generate new images, I see no reason why those new images should inherit any copyrights from the original image if the resulting images look sufficiently different. (Obviously, if you just train on 1000 images of Mickey Mouse, you'll get m…

Looks like its just copy pasting in code from ingested repos to me

https://twitter.com/mitsuhiko/status/1410886329924194309

Re: Is GitHub Copilot a blessing, or a curse?

#172

Earlier quoted context omitted.

The following is just my opinion, and I'm not that hard-set in case anyone has any nice arguments. Generally, when you (for example) use GANs to learn from (copyrighted) images and generate new images, I see no reason why those new images should inherit any copyrights from the original image if the resulting images look sufficiently different. (Obviously, if you just train on 1000 images of Mickey Mouse, you'll get m…

> Humans work the same way This is the fundamental issue. They don't. You can't sneak a camera into a cinema saying "don't worry, it works just like human eyes". Neural nets aren't neurons.

For a while, recording a movie was absolutely legal in Canada.

Re: Is GitHub Copilot a blessing, or a curse?

#173
post #120

Earlier quoted context omitted.

We can't know the future, but we guess based on past trends. Technology has been pretty good at replacing humans in the past, and a lot of times we've said "a machine can't do this" and been wrong. We'll have to see, but I think it's silly to say it's not working now so it never will.

We've heard breathless claims that AI will replace people coding ever since the advent of AI in some form or another. If we truly were going on past trends, we would conclude it is not very useful and will probably stay that way.

Do you think Copilot doesn't represent a step forward since the advent of AI?

Re: Is GitHub Copilot a blessing, or a curse?

#174
post #36

Earlier quoted context omitted.

Copilot is also almost certainly going to become better. For example, NVIDIA's DLSS was viewed as a failure at launch, but now it's almost magic in terms of offering better results at a lower performance cost.

It might also become worse. It seems to me that GitHub has opened themselves (well, this Copilot thing anyway) up to a form of DoS attack: Just imagine what might happen if a bunch of people opened up a number of public repos filled with utter crap? Not suggesting anything, here, just musing on a possibility.

Well, that's a solvable problem. You just need a classifier to filter good code from bad. I would imagine they're already using analytics on the popularity/usage of the repos to weight the training data.

Re: Is GitHub Copilot a blessing, or a curse?

#175
post #76
post #36

Earlier quoted context omitted.

Copilot is also almost certainly going to become better. For example, NVIDIA's DLSS was viewed as a failure at launch, but now it's almost magic in terms of offering better results at a lower performance cost.

To me graphic seems to have a very specific goal of rendering more details & better simulation of real world. People aren't even agreed on what is "good" code.

Yeah but only software engineers care about "good" code. Everyone else just wants their software to do it's job. If you can train AI to write code which is going to get the right outputs, it will win.

AI can probably also beat humans in terms of things like performance optimization. An AI can write code a human never would. We have to write short functions and well-factored code which fits in the human brain. An AI could theoretically write millions of lines of highly-specialized spaghetti which is perfectly correct and perfectly optimized.

Re: Is GitHub Copilot a blessing, or a curse?

#176

Copilot was made from stealing code on Github, ignoring the licenses set on repos such as e.g GPLv2, using AI as a trick to license-launder code. Copilot has announced their plans to become a paid service. So this product that would not be possible without public, open-source code will itself be non-public, closed-source, closed-data. It is extracting value from the commons and funneling it to a private company.

The following is just my opinion, and I'm not that hard-set in case anyone has any nice arguments. Generally, when you (for example) use GANs to learn from (copyrighted) images and generate new images, I see no reason why those new images should inherit any copyrights from the original image if the resulting images look sufficiently different. (Obviously, if you just train on 1000 images of Mickey Mouse, you'll get m…

I think the catch is, a human is considered a creative being, as in it can create new content which consequently is copyrighted to that human. An AI cannot - at least so far - not create create genuinely new content and also cannot assume copyright.

If the copilot would have been trained on open source software e.g. to discover bugs, bad code style, or other things "learned" by analyzing existing code and using the results of this analysis as a metric for judging code, it wouldn't be a copyright problem. But creating new code based on what it "learned" is a much more difficult field, especially, if it is "quoting" so literally.

Re: Is GitHub Copilot a blessing, or a curse?

#177

Earlier quoted context omitted.

Do you have a link discussing how it does? Ive only seen an article from a lawyer explaining how it doesn’t, in their professional opinion.

Regardless of the nuances of that point, GitHub copilot violates copyright because the content it was trained on still lives in it, and you can get it to spit it out verbatim. If I were a master artist, my existence wouldn’t violate copyright, but I would certainly be violating it every time I chose to reproduce a copyrighted work for a client.

Okay but do any lawyers agree with you?

Re: Is GitHub Copilot a blessing, or a curse?

#178
post #173

Earlier quoted context omitted.

We've heard breathless claims that AI will replace people coding ever since the advent of AI in some form or another. If we truly were going on past trends, we would conclude it is not very useful and will probably stay that way.

Do you think Copilot doesn't represent a step forward since the advent of AI?

[deleted]

Re: Is GitHub Copilot a blessing, or a curse?

#179
post #89
post #83

Earlier quoted context omitted.

I as an open source author absolutely do not want Microsoft to get richer from using my code, code that I contributed or published for the benefits of other developers. They took my work, removed my name and trained an advanced pattern matching technique to try to make code like mine and then sell it. It’s so obviously ethically questionable it’s insane. Developers are absolutely pissed about this, and rightfully so.

Not even copyleft licenses prohibit somebody from earning money from what you released, and that includes Microsoft. The idea behind free software is that it benefits all users equally, even if other developers get the biggest direct benefit. The best question to ask yourself is if you would be annoyed as much if a company like Black Duck did a similar training or analysis with their OpenHub (openhub.net)? I think on…

CC-BY-NC explicitly prohibits commercial usage.

It’s also common to see GPL license for non-commercial usage and paid licenses for commercial usage.

Re: Is GitHub Copilot a blessing, or a curse?

#180
post #126

Earlier quoted context omitted.

"AI training" is not a "training" in human sense. It's algorithm. > In other words, I don't think using of an algorithm on copyrighted code violates copyright It does.

Do you have a link discussing how it does? Ive only seen an article from a lawyer explaining how it doesn’t, in their professional opinion.

«A derivative work is based on a work that has already been copyrighted. The new work arises—or derives—from the previous work.

If you own the copyright to a work, you need to be aware that you also have rights to derivative works. If you're considering incorporating someone else's work into your new work, you need to be aware that you may be violating the copyright to the original work.»

https://www.legalzoom.com/articles/what-are-derivative-works...

Post reply on HN