It's your own fault for using anything made by microsoft at this point.
VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
471–480 of 917 posts
Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
#472Earlier quoted context omitted.
Can you explain how this works? Doesn’t this also stop you from connecting to it over ssh via vs code?
Yes that's the point. If vscode didn't insist on installing potentially gigabytes of blobs then this wouldn't be necessary. (I'm a vimmer anyway... And emacs is too bloated to fit too, conveniently.)
If you connect via ssh, you could use Tramp. It does not install emacs on the target, but instead use a somewhat permanent connection as a tunnel for most emacs commands (transparently). Works too with docker, podman, distrobox, etc,...
Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
#473Earlier quoted context omitted.
If i remember chrome:// used to have special meaning in Firefox (and probably well before that), and was used to tweak UI settings. I always assumed this was where Google took the name from.
Chrome is a now-somewhat-archaic term for GUI (or specifically the actual elements of the GUI, not the concept), and Netscape/Mozilla did use the term a lot. Google claims that their browser is called Chrome because of an association with fast cars (presumably Google was keen to market it to extremely old people, chrome not having been a particularly big thing in cars for a very long time).
Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
#474Earlier quoted context omitted.
Interesting case: - a project manager vibe-coded the change without thinking it through at all - the PR was reviewed by an LLM - an actual engineer gave LGTM without really reviewing the changes, trusting the LLM Did I get this right?
The LLM actually points out the problem tho
Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
#475I miss in this whole thread why this is happening. Presumably to be transparent whether code has been co-written by AI? What's in it for Microsoft? If we accept that AI can't copyright or own IP rights on something, then why? I have a sneaky suspicion that there's some lobbying in the works to overturn that ruling going forward. In the past, it was OK to build models from copyrighted data etc one might have found on…
Most odd things can be explained by imagining who might be able to buy a new boat as a result.
Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
#476Earlier quoted context omitted.
It's a complete takeover of technically incompetent management that feels like it can finally execute their ideas to the fullest instead of relying on those pesky swengs with their obstructions, complaints and problems. We'll soon get the management utopia everywhere.
On the other hand, no one to place the blame on if management does it themselves.
There's always people for management to blame. That's the great part of being management.
By definition, there's someone/thing you're managing that you can pass the blame onto.
Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
#477Earlier quoted context omitted.
Perennial HN trope: all bad tech evolutions are management's fault. Engineers are flawless paragons of technical purity.
Hard to blame the engineer when the engineer gets fired for not implementing management's whims. As much as I'd like to hold people accountable and say they should just accept getting fired instead of compromising the ideals, the truth is I've got a family now and if they paid me enough I'd do the same.
It couldn't exist without engineers.
Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
#478I am the person who approved this PR and would like to acknowledge and apologize for the mistake of turning this feature on by default without sufficient upfront validation. There was no ill intent by evil corporation, but rather a desire to support functionality that some customers expect of VS Code w.r.t. AI-generated code. As folks mentioned here - many similar tools do this as well. Obviously, it should not be on…
Here's one:
I think a senior sysadmin needs to sit you down in their office and have a very serious talk with you about the responsibility that comes with writing code other people run. I am serious. We used to have these talks with everyone who got sudo access. You shouldn't be shipping code if you don't understand the trust that is required of people in your position.
This isn't just about this "feature" being active when AI features are disabled, the way you mis-implemented this has resulted in it modifying the commit message with the user even seeing it! That is malicious behavior, not an innocent little feature "to make life easier".
I've fully switched off of VS Code to Kate now, which is faster and better behaved in most cases anyway. Bye.
Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
#479Earlier quoted context omitted.
I agree with you in very general terms, but I'm not sure you can reach the level of "market share" VSCode has had the last few years with just the very young .
True that. No question VSCode has some real structural advantages: free (as opposed to pricey VS Enterprise licenses - this matters in non-tech enterprises), somehow easily installable even in enterprise locked-down environments, first-class webdev support, first-class python integration, extensive extension/plugin ecosystem, extensive multi-language support, excellent wsl integration, and that MIT source license to…
Maybe in some areas this is true. But there are and long have been a lot of really good text editors in the world. All it takes is a pretty mild preference for free software in this case.
Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
#480I am the person who approved this PR and would like to acknowledge and apologize for the mistake of turning this feature on by default without sufficient upfront validation. There was no ill intent by evil corporation, but rather a desire to support functionality that some customers expect of VS Code w.r.t. AI-generated code. As folks mentioned here - many similar tools do this as well. Obviously, it should not be on…
> I am open to any (constructive) comments/suggestions Here's one: I think a senior sysadmin needs to sit you down in their office and have a very serious talk with you about the responsibility that comes with writing code other people run. I am serious. We used to have these talks with everyone who got sudo access. You shouldn't be shipping code if you don't understand the trust that is required of people in your po…
Seethe