I didn't envision that my code would be split into tons of little code snippets and then sold around. Doing so, the spirit of the GPL-isation of my software has been betrayed.
There's also a free flow of information argument. Citing pieces of my code is good for that flow. But MSFT doesn't seek free flow here, it seeks a money-making flow. So I disagree.
I understand your explanation and somehow, it sounds right on the pragmatic level. But on the idealistic level, it sounds wrong :-/
Dunno...
On balance, you are distributing software that is copyrighted (nothing you can do about that). The GPL gives users some limited permissions that undo some of the restrictions that come with copyright. Fair use applies to copyrighted material regardless of the license and is not something you can actually restrict with a license. That kind of is the whole point of fair use. So, the GPL, it's (supposed) intentions, and idealism don't factor into the equation here. That's just not how it works.
Sorry to burst your bubble.
It certainly does. That's one big reason why judges often disagree and judges' rulings can often be predicted by which party appointed them.
But the copyleft ideology in particular rarely factors into court cases, because few judges care about it.
Or maybe I've misread the article?
I suppose this is how e.g. Red Hat operates.
In the same way, Google is making use of fair use by providing website titles, summaries, book samples, etc. There has been some controversy with news about them taking that too far. But by and large, they are still legal. And people of course have tried to challenge that in courts. It's just small samples being distributed, not a complete work. There are lots of examples of companies depending on fair use for all sorts of things. E.g. quoting an author or paraphrasing their work is fine. You don't need their permission for that.
Also another point here is that it isn't necessarily just MS that would be violating copyright (if the above somehow wasn't the case) but the receiver of the auto-completed code that ends up distributing that code. Because it is that code that ends up being distributed. All MS does is show you some code sample, it's the programmer that decides what to do with it. Whether you receive your sample from Stackoverflow, co-pilot, or a book is not relevant: you are responsible for the code you distribute.
Finally, the Github terms of use give Github some rights to doing things to your code if you choose to put it on Github. That probably also covers what they are doing with Github Co-pilot. That's a valid reason for removing your code from Github if you don't agree with that but of course no guarantee that Github Co-pilot would not crawl external public git repositories or that whomever you pick as an alternative wouldn't have some similar legalese in their terms of use. If these things matter to you, review it. Just because Gitlab hasn't launched a co-pilot competitor doesn't mean they couldn't.