For people like me forced to come over from Visual Studio and other editors, it's a huge step down.
For example, instead of making improvements to the PowerShell Integrated Scripting Environment (ISE), Microsoft marked it as deprecated and "forced" everyone over to Visual Studio Code, whether they like it or not. E.g.: it's the only Microsoft IDE with PowerShell Core (pwsh) support.
Despite being the only supported Microsoft PowerShell IDE, VS Code does not play nice with PowerShell. For example, if I open Code, it opens three(3!) PowerShell terminals for unfathomable reasons. One of those starts with errors, the other works, but the third one is the default and crashes if you look at it sideways. Tab-complete just... stops. Even when tab-complete "works", it'll often start mid way through the list, hiding all of the relevant items and showing your random garbage like "quick start snippets" that make zero sense in the given tab-complete context.
I could rant for hours on how poor the Visual Studio Code quality is, but nobody will listen, because for people upgrading from Notepad, it's the second coming of Jesus.
Then there's always the smart-ass that explains patiently that this is all my fault for not "customising" my VS Code experience with JSON configuration settings that are seven levels deep and documented only in some blog article from three years ago. Meanwhile, I've never had to customise anything in Visual Studio. It "just works" the way you'd expect a Windows application to work. Not some Linux-Windows hybrid intended to be the "embrace" part of the unholy "embrace-extend-extinguish" trio.