@aks@scalie.zone
Update:
Microsoft has reverted the change and has made an explanation:
https://github.com/microsoft/vscode/issues/31431
There was a bug in the code that was not found in testing that attributed non-Copilot code completions to Copilot.
Yeah sure, but the actual problem was turning on Copilot co-attribution by default in the first place!
It gets even worse when looking at The Orange Site thread.
This was caught in testing, but MS developers underestimated the impact:
https://news.ycombinator.com/item?id=47994193
Look I'm not a lawyer or legal expert, but how'd nobody over there even consider that this could've been legally or morally dubious at least?
Oh and in another reply, the same MS employee says that the supposed bug slipped through testing:
https://news.ycombinator.com/item?id=47994074
Which one is it, the behaviour slipped through testing or was caught in testing but not addressed?
Whether this whole mess was due to incompetence or malice, either way this is a very damning indictment on the VSCode team's part. They either knew what they were doing the first time around and are backtracking or their processes are in dire need of a revamp if not a single person in the chain stopped the change from going public, much less getting merged.