Earlier quoted context omitted.
> Microsoft spent literal decades rehabilitating their reputation. And then set fire to the whole thing in an offering to their robot gods. When did this happen?
When they started embracing and using Linux, WSL is pretty good. But it doesn't completely wash out it's past.
VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
711–720 of 917 posts
Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
#712Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
#713Earlier quoted context omitted.
> Microsoft spent literal decades rehabilitating their reputation. And then set fire to the whole thing in an offering to their robot gods. Probably they thought the new generations forgot about how awful they were in the not so distant past. I think they set it all on fire because greed got the better of them again.
> 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…
Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
#714Earlier quoted context omitted.
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).
Why is it archaic? It's part of the same metaphor as "engine", which is still widely used.
Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
#715The best part is that copilot commented on the PR saying that this doesn’t actually change the behaviour, creates inconsistency in the codebase and suggested reverting the change! (This comment seems to have been ignored…) > The configuration schema default was changed to "all", but the runtime fallback in extensions/git/src/repository.ts still calls config.get('addAICoAuthor', 'off'). This is now out of sync and can…
Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
#716Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
#717Earlier 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.
Aren't you guys glad there are no programmers gatekeeping programming with their "morals" and "etiquette"? Any marketer with an LLM can update the programming tool now. AI really levels the playing field and it's time for pesky programmers to get off their high horse, don't you think? :)
Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
#718Earlier quoted context omitted.
I saw a trend of UX/UI designers coming with practice which I knew better were wrong. But they insisted. E.g hijack brosser native controls. Will never know whether they passed along some manager/PM commandements or were just incompetent.
> But they insisted. E.g hijack brosser native controls. [Rant-Example] The goshdarn ticketing-system hijacks alt-f, so that instead of opening the F ile menu of my browser, and instead toggles the favorite-status of whatever ticket I happen to be viewing.
Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
#719Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
#720I 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…
And another thing is, why was there absolutely no pushback from your part on any of the issues with the original PR, and why it was merged within hours in that state?