39 comments

[ 3.1 ms ] story [ 53.4 ms ] thread
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.

I gave up and installed Rider. So far so good.

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.

Maybe I should consider rider...

Microsoft VS peaked for me in 2013 to 2017 when they decoupled a bunch of things, specifically .NET
.NET feels better than ever right now. C# native type unions maybe next year will be a big highlight.
I wonder if 30% of their code being written by AI has anything to do with it
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
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.

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...

Reminds me of Windows Search.

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.

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.
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.
It's because Tab accepts copilot suggestion, you have to press Enter instead to accept the language server suggestion.
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.

Shout-out to FileLocator Pro as an aside.

Jetbrains Rider is very nice. Especially with ideavim plugin.

And pretty fast these fast these days.

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.
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.

Don't get me started on powershell!

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.

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.
Why do people still spend time worrying about M$ stuff…
I switched from Sublime to VSCode years ago and have been fairly happy but the recent AI onslaught in VSCode is making me look at other editors.
> Ivan was born at a very young age, this has made a lot of people very angry and is widely regarded as a bad move.

Lol

Is there a GitHub issue for this?
C# DevKit has been doing this for the last month or so I’ve noticed.

Sometimes it’s fine, sometimes it’s algebra. I know VSCode replaced their autocomplete with copilot but whaaaat?

Change to real Visual Studio for C#. Visual Studio Code is complete garbage in comparison.
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.
Another thing I'd like the team to fix, is to ignore autocomplete for ., -> and other operators in comments, or ignore all autocomplete in comments. VSCode does have the option, but at least for my C code, it only works for // comments, not /* */ ones.
Someone needs to bring back the old "Windows [Aero] Task Force" website from back in the Vista/XP days that listed every minor UI/UX annoyance in Windows.

And Jobs knows we need something like that for macOS and iOS too now.

iOS autocomplete for the longest time was just absolutely insane. It would inject the selected suggested option into the middle of a word when I was correcting a spelling error. Really made me feel like I was doing something weird but I swear I was being normal for once.