This is actually bearable compared to the new terminal suggestions in vscode. Not only does it autosuggest bizzare completions for commands, it breaks shell completions. So when I tab a file path, it shoves the absolute path into the partially typed path making it unusable.
Yeah for anyone else (especially Mac and Linux users) who recently had this frustration thrust upon you: Go into VSCode settings and search for terminal integration > uncheck.
Recent changes have been a little invasive. The terminal auto complete was a week or so ago, and the popular Gitlens extension also recently pushed a really poor rebase interface. Besides those two in the last weeks, I can't remember any time VS Code has messed up my workflows so badly.
Nope, not crazy. Pretty much solely used it for years but got a lazyvim* setup last week
Still has excellent integrated debugging and is more familiar than nvim, but it has really started to get in its own way the past couple minor versions
*Not "lazy I'm" (though perhaps I am for letting that slide)
I don’t know what it is but I think commpletion across editors has gotten so much worse. Even PyCharm now routinely completes some hallucinated method or library. Even with AI completions off I feel like it still somehow got dumber since 2023.
Intellisense + Intellicode + Roslynator (extension) combined were really the height of productivity in Visual Studio. Now they've driven a steam-roller over all of that, forced CoPilot down our throats.
I LIKE CoPilot's "chat" interface, and agents are fine too (although Claude in VS Code is tons better), but CoPilot auto-complete is negative value and shouldn't be used.
Huh I'm the opposite. I find the copilot chat slow and low value compared to ChatGPT. But I use the tab autocomplete a lot.
Otoh I disabled all the intellisense stuff so I don't have the issues described in TFA: tab is always copilot autocomplete for whatever it shows in grey.
I hate the time unpredictability of it. Intellij also has AI completion suggestions, and sometimes they're really useful. But sometimes when I expect them, they don't come. Or they briefly flash and then disappear.
What would be nice is if you could ask for a suggestion with one key, so it's there when I want it, and not when I don't. That would put me in control. Instead I feel subjected to these completely random whims of the AI.
For one, it's the right arrow key for complete for most things (but tab for others).
But by FAR the worst thing is that often times you'll type a command and try to tab/arrow complete an argument, and the module/dll or whatever is not loaded into memory, and so theres some blocking operation and loads the module which takes 10+ seconds. This happens to me almost every day.
I do love powershell otherwise though, after 20+ years in bash, there is actually some things to like about it.
If you like Powershell but have some complaints, you might find nushell to be the best of both worlds. My elevator pitch for it would be imagine the object-oriented / typed nature of Powershell, minus the verbosity and windows-centric design of it. As someone who develops on and for windows computers, nushell is a real breath of fresh air.
I have a command line program at work which outputs json. Pure JSON in all situations.
I thought nushell would be able to make sense of that and display it semi-nicely.
Nushell pukes on it, errors out, and doesn’t even show the output of the command. As far as sins go for a shell, not showing the output of the program it just ran is very high among them.
With external commands you might have to collect the output of the program before doing any sort of manipulation. I’ve been got by this before too; the fix is simple (for me at least). `external.exe | collect | from json` et voila
I like PowerShell too, but in what universe other than ours (clearly the worst one) is it even possible for loading a module to take more time than the blink of an eye?
Microsoft should find it embarrassing how long it takes powershell to load a module. Pushing <tab> to autocomplete a cmdlet name should never take more than maybe 100 milliseconds.
Windows Search requires a DNS lookup, and HTTP request to start your search, as a direct result if either one of those is slow the whole UI lags and hangs. It hasn't ever been fixed in Windows 11.
Also, there is a RegX way of disabling "bing" for-real in the search but they released an update that caused doing so to break search entirely if that was set (totally a coincidence I'm sure).
I have resorted to installing my laptop with Ireland / English & later switching the region to US / English. That way it's considered part of the European Economic Area.
Which allows me to disable web search in start, disable widgets, etc.
Windows Vista/7, search was instant and correct (modulo hard drive speed and RAM). Then Windows 10 came along, I click a local result, half the time it takes forever to open Explorer, or nothing happens, or there's no results once it does open.
By the way, things still work correctly and instantly with OpenShell, so something still works underneath whatever shit veneer has coated the shell
Let me fix the title: Microsoft, please get your shit together
I tried to help a relative set up a new Windows PC recently and had to give up. Everything was confusing and/or broken, and for the first time I am ready to just send them to Apple. A literal brand new PC with nothing installed, and after logging in, clicking Explorer in the task bar doesn't work and I have to reboot and try again? I'm not even angry, just disappointed.
Did you know there's no more Office, they literally call it Microsoft Copilot 365 now? Like, I've been through shades of this before (".NET", anyone?) but it's a thoroughly unhinged clusterfuck on an entirely different level now.
I'm convinced that the win10 Start Menu was the single worst thing microsoft inflicted upon us in that OS. I imagine that particular discussion went like this:
Exec1:"We have a semi decent os with a refreshingly updated UI that should stay relevant for a decade. How can we make it better?"
Exec2: "why not replace the perfectly good start menu we have with an ugly, oddly proportioned rectangle with animated ads for our products."
Exec3: "Sounds
great! Just make sure
it has a quarter of the information density of the old one and takes up twice the screen space."
I haven't used Win11 enough to discover how they have managed to further degrade the experience, but at least it looks nicer.
There was a time when if you edited documentation in vscode and had copilot on it would complete internal user and project names when it encountered a path on some.random LLM project we were building. I could find people and their projects by just googling the username and contextual keywords.
We all had a lot of laughs with tab auto complete and wondered in anticipation what ridiculous stuff it threw up next.
30% of code written by AI, but 100% of tools must be enshittified with the terrible and behind Microsoft Copilot even if it means you will blow up the goodwill for VS Code in a matter of months
I really hate that by default all of these tools perform completion with tab. It makes it very difficult to add indentation. It's not a problem with traditional autocomplete because you either need to already have a character typed before the cursor, or to have manually summoned the completions. But these AI autocompletes will try to generate code on completely empty lines, so you think you're pressing tab to get an indent and instead end up with code you did not want.
Looks like Unity code. Not sure if it’s Visual Studio or VS Code, but yeah, it was baffling to me how weirdly bad C# support in either IDE is. Maybe something wrong with my setup, but autocompletions indeed suck (in addition to just wrong picks, editors often would suggest a symbol that doesn’t make sense from the typing perspective, as if there aren’t any language servers or intellisense or whatever).
VS code would also eat up the curly brace at the end of a class declaration when auto-generating a method skeleton.
They say it's vscode in the article. I can't say I've seen anything that egregious happen with unity in visual studio.
It's stuff like this though that keeps me from using vscode for code editing (I use it for markdown and JSON file editing only). I guess I don't know what I'm missing but it's never been a smooth experience for me. If I'm on Windows I tend to stick with visual studio.
Pretty sure you’re supposed to press return in order to accept a dropdown suggestion. Tab is for accepting the AI code completion. I disabled completions.
Pretty sure they hijacked a key most developers had a muscle memory of using since Visual Basic 6 to pump their AI usage metrics, and then invented a workaround that requires re-learning their tool.
Not a very clear issue report, but looks like a conflict between language features, copilot, and possibly snippets?
The project is open source and invites feedback in the form of issues, although sadly their issue report page is a bit of a cesspool - will really make you lose faith in humanity.
I think maybe vibe coders got to it and don’t realize that there are certain requirements to create useful feedback? Or maybe VS Code linking from the help menu is a bad idea.
This blog post is a step above the “doesn’t work is garbage” issues filed in GitHub, but only just one. What did the author try to fix? When did it stop working? What kind of projects? What extensions are installed?
> Not a very clear issue report, but looks like a conflict between language features, copilot, and possibly snippets?
Which is overwhelmingly the VS Code experience for any language. Everything feels shaky. I've had to report a bunch of irritating issues like the post for TypeScript - never fixed or resolved. I have never needed to report issues like this for C# in Visual Studio, and when I have tried C# in VS Code the experience makes me wonder if it's a bad joke.
Visual Studio has been doing wacky stuff to me like this when I am trying to start a LINQ statement and type a letter to be the lambda variable like Select(f => … but when I hit ‘f’ it just autocompletes some random model from some .NET api that starts with F that I then have to delete because why would I want FileStreamCombulator right now I’m trying to start a lambda??? and don’t remember it doing this in the past.
This is a company that cannot get "basic file search" working on their OS for 30+ years, I'm hardly holding my breath as they double-down on overcomplexity with even more overcomplexity.
Not a fan of Windows either, but playing devil’s advocate here: Apple’s Finder has steadily gotten worse over the last ~16 years, at least in my experience. It increasingly struggles with basic functionality.
There seems to be a pattern where higher market cap correlates with worse ~~tech~~ fundamentals.
why would a company be incentivized to improve the user experience in ways that aren't profitable ? especially after watching the number one tech company literally worsen UX to increase profitability
Has there been a change lately and in the project, or is it just internet bias?
Still has excellent integrated debugging and is more familiar than nvim, but it has really started to get in its own way the past couple minor versions
*Not "lazy I'm" (though perhaps I am for letting that slide)
Intellisense + Intellicode + Roslynator (extension) combined were really the height of productivity in Visual Studio. Now they've driven a steam-roller over all of that, forced CoPilot down our throats.
I LIKE CoPilot's "chat" interface, and agents are fine too (although Claude in VS Code is tons better), but CoPilot auto-complete is negative value and shouldn't be used.
Otoh I disabled all the intellisense stuff so I don't have the issues described in TFA: tab is always copilot autocomplete for whatever it shows in grey.
What would be nice is if you could ask for a suggestion with one key, so it's there when I want it, and not when I don't. That would put me in control. Instead I feel subjected to these completely random whims of the AI.
For one, it's the right arrow key for complete for most things (but tab for others).
But by FAR the worst thing is that often times you'll type a command and try to tab/arrow complete an argument, and the module/dll or whatever is not loaded into memory, and so theres some blocking operation and loads the module which takes 10+ seconds. This happens to me almost every day.
I do love powershell otherwise though, after 20+ years in bash, there is actually some things to like about it.
I thought nushell would be able to make sense of that and display it semi-nicely.
Nushell pukes on it, errors out, and doesn’t even show the output of the command. As far as sins go for a shell, not showing the output of the program it just ran is very high among them.
nushell had its chance with me.
It is amazing until you run into one of these insane behaviors that somehow nobody ever fixed.
(Some are actually fixed finally in 7.x - like issues with filenames with grave characters in them)
Microsoft should find it embarrassing how long it takes powershell to load a module. Pushing <tab> to autocomplete a cmdlet name should never take more than maybe 100 milliseconds.
It's been botched since they added ads to the Start Menu.
Pretty soon VSCode will show you intellisense ads in the list of code completions.
Also, there is a RegX way of disabling "bing" for-real in the search but they released an update that caused doing so to break search entirely if that was set (totally a coincidence I'm sure).
Which allows me to disable web search in start, disable widgets, etc.
https://github.com/musman96/win11debloat
Windows Vista/7, search was instant and correct (modulo hard drive speed and RAM). Then Windows 10 came along, I click a local result, half the time it takes forever to open Explorer, or nothing happens, or there's no results once it does open.
By the way, things still work correctly and instantly with OpenShell, so something still works underneath whatever shit veneer has coated the shell
Let me fix the title: Microsoft, please get your shit together
I tried to help a relative set up a new Windows PC recently and had to give up. Everything was confusing and/or broken, and for the first time I am ready to just send them to Apple. A literal brand new PC with nothing installed, and after logging in, clicking Explorer in the task bar doesn't work and I have to reboot and try again? I'm not even angry, just disappointed.
Did you know there's no more Office, they literally call it Microsoft Copilot 365 now? Like, I've been through shades of this before (".NET", anyone?) but it's a thoroughly unhinged clusterfuck on an entirely different level now.
Exec1:"We have a semi decent os with a refreshingly updated UI that should stay relevant for a decade. How can we make it better?"
Exec2: "why not replace the perfectly good start menu we have with an ugly, oddly proportioned rectangle with animated ads for our products."
Exec3: "Sounds great! Just make sure it has a quarter of the information density of the old one and takes up twice the screen space."
I haven't used Win11 enough to discover how they have managed to further degrade the experience, but at least it looks nicer.
We all had a lot of laughs with tab auto complete and wondered in anticipation what ridiculous stuff it threw up next.
Sometimes it’s fine, sometimes it’s algebra. I know VSCode replaced their autocomplete with copilot but whaaaat?
VS code would also eat up the curly brace at the end of a class declaration when auto-generating a method skeleton.
I gave up and installed Rider. So far so good.
It's stuff like this though that keeps me from using vscode for code editing (I use it for markdown and JSON file editing only). I guess I don't know what I'm missing but it's never been a smooth experience for me. If I'm on Windows I tend to stick with visual studio.
Maybe I should consider rider...
Also there is the VC money problem with Zed, at some point, that money will want returns on every dollar spent.
2. That's fine, they'll just build some cloud feature
The project is open source and invites feedback in the form of issues, although sadly their issue report page is a bit of a cesspool - will really make you lose faith in humanity.
https://github.com/microsoft/vscode/issues
I think maybe vibe coders got to it and don’t realize that there are certain requirements to create useful feedback? Or maybe VS Code linking from the help menu is a bad idea.
This blog post is a step above the “doesn’t work is garbage” issues filed in GitHub, but only just one. What did the author try to fix? When did it stop working? What kind of projects? What extensions are installed?
Aside: in the spirit of Christmas cheer, I’ll share this fun meme, completely (un)related to the topic at hand: https://old.reddit.com/r/github/comments/1at9br4/i_am_new_to...
Which is overwhelmingly the VS Code experience for any language. Everything feels shaky. I've had to report a bunch of irritating issues like the post for TypeScript - never fixed or resolved. I have never needed to report issues like this for C# in Visual Studio, and when I have tried C# in VS Code the experience makes me wonder if it's a bad joke.
And pretty fast these fast these days.
Lol
Shout-out to FileLocator Pro as an aside.
There seems to be a pattern where higher market cap correlates with worse ~~tech~~ fundamentals.