- Automatically activated audio cues (purportedly for accessibility) without consideration for users with auditory sensitivity; continued to release changes that would override attempts to disable the unwanted sound; dismissed with "but how else could we possibly notify people that we added the feature?"

- Refusing for over seven years to offer a simple UI to clear "issues" pane, instead blaming plugin authors for not 'owning' the content. https://github.com/microsoft/vscode/issues/66982

Microsoft hasn't cared about the actual users of VSCode for a very long time.

I'd like my tools to not have a time-bomb attached to them, no matter if it takes 10 years to explode.

And honestly I think this case is just a perpetually clueless manager getting over-joyous with vibecoding (to the point of being marveled at changing two lines of code without blowing everything up).

It's probably going to be reverted in the coming days. Which doesn't change the fact that it's a very Microsoft way of operating.

Just because you can opt out doesn't mean that they're not shitty for defaulting you to opt in.