Earlier quoted context omitted.
First, revert the commit, then apologise.
I did both, didn't I? :-)
At the time of writing it wasn’t reverted, but thank you for replying.
VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
761–770 of 917 posts
Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
#762Earlier quoted context omitted.
> greed Is a greed/not greed scale really useful to discuss company behaviors ? I wanted to say I get what you mean, but even thinking about the company I root for the most, I can't think of a point where they're not driven by their desire to make a lot more money. If your point is that there's good and bad ways to seek money, I'm not sure it's properly encompassed by "greed", which I interpret as the intensity of a…
The Seven Deadly Sins provide an interesting perspective to human psychology even in modern times. Greed / avarice is defined as wanting more than you need.
Who decides how much you need?
Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
#763Earlier quoted context omitted.
When they started embracing and using Linux, WSL is pretty good. But it doesn't completely wash out it's past.
Dotnet core was also a move in that direction with large portions being open source.
That wasn't rehabilitation, they just wanted to save the dying platform.
Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
#764Earlier quoted context omitted.
That’s not an accurate take. Microsoft has had a monopoly on the PC desktop OS. Anyone writing applications for users was targeting Windows and using Microsoft. To call most of these developers “not serious” is quite and overstatement. This includes all PC game developers, DAW, CAD, Adobe…? Azure expanded the Microsoft franchise, and provides another prong to their whole integration story just like cloud AD services…
> Anyone writing applications for users was targeting Windows and using Microsoft. Developers as users, sure. MSFT was common. Developers as responsible for infrastructure, MSFT anything was considered a huge risk and unreliable in the 90s. Granted, my memory retains only a general narrative...I remember a shift by 2002ish when I started to see windows servers as perfectly fine machines for closet/under-the-table inf…
I think the first shift was the reckoning with Windows NT actually being decent software. Windows 2000 (AKA NT 5.0) included Active Directory, WebDAV support, and a host of other features that were genuinely useful in a sysadmin setting [0]. Also, it shipped with IE5 which introduced XMLHttpRequest and was the best web browser by a mile. Between their pushy sales reps and so much stuff being included by default, I think it got kind of hard to push for anything else for a while.
Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
#765Earlier quoted context omitted.
I mean that they’re not necessarily part of the --message parameter to `git commit`, but instead part of the --trailer parameter. I don’t know how VSCode is programmed, but it seems plausible that trailers are handled separately from the message parameter. https://git-scm.com/docs/git-commit
We're talking about Git here. The question is not "how VSCode is programmed", the question is "does Git have a special field for commit trailers". The answer is no. Git stores the trailer as part of the commit message.
If you look at the comment I’m responding to, it is in fact about how VSCode is programmed; specifically, a possible reason why the Co-Authored-By trailer doesn’t show up in VSCode’s commit message box.
Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
#766Earlier quoted context omitted.
> If you fell for this once again, there's nobody else to blame but yourself. We don’t need snarky comments like this, especially when the technology in question is so pervasive and takes a lot of cognitive effort to avoid. The blame lies solely with Microsoft.
What you call snarky , I call individual accountability .
Should preventing inhaling smoke in public spaces be also individual accountability?
Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
#767Earlier quoted context omitted.
Not that simple… this is great read: https://legallayer.substack.com/p/who-owns-the-claude-code-w...
Still if you're the lawyer on the side of the lawsuit claiming that the code is copyrightable, you really don't want that copilot attribution in the commit message muddying the waters.
you actually do, as counter-intuitive as that seems. co-authored implies (and gives you room to argue) that you were involved in the process. hiding the fact that you did if proven otherwise (not that hard to prove in many cases if it comes to that) won’t be looking good. at my work, we are mandated to include AI attribution and I would say every well-run company should have same mandate
Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
#768Earlier quoted context omitted.
The torment nexus was built by engineers. Not management. It couldn't exist without engineers.
Nuclear bomb was built by scientists and they weren't the one that fired it, what's your point?
Their point, however, is perfectly clear - it’s practically obvious. No one forced them at gunpoint (unlike those scientists, figuratively speaking). Why are you pretending not to understand?
Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
#769Incredible. I would like to study the of people who thought it is a good idea. Reading comments on GitHub made me laugh. Made me also wonder, what's the next step?
It would be to starting giving a chance to other competitors. I have been very comfortable zed except for 2 issues (on Linux). After they are resolved, I will probably start using it 100% of the time.
Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
#770Earlier quoted context omitted.
Principal engineer balks at bad UX when the PM should know better (it's their job) 2023: Ah well I guess we can't do it 2025: you're fired. Hey kid we hired two weeks ago, implement bad idea please
To be fair, it was already done by bad managers long before.
This is what I sees getting missed in a lot of LLM conversations. They're amplifiers. Full stop. If you have good practices they supercharge them, if you had bad practices, same thing.