Hacker News Reader

Comment by torben-friis | Hacker News Reader

It’s so weird, vscode worked flawlessly for me for years and after migrating to neovim a month or two ago I keep seeing complains.

Has there been a change lately and in the project, or is it just internet bias?

View on HN

I've seen some weird breakage recently in vscode. The C++ support failing to parse sources correctly (for LLVM), Rust debugging no longer showing vectors properly. Not sure if this is some bizarre interaction with my setup (which is pretty vanilla Ubuntu) or a regression in basic functionality brought on by an over-emphasis on AI features.

It is worrying that for many months now, pretty much all the content of changelogs has been about AI.

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.

I remember thinking wtf when Python import suggestions became disabled by default.

https://github.com/microsoft/pylance-release/issues/3579

It does weird stuff. I've bitched about it do much to my workmates until they disabled autoformat features wich cause 5k line conflicts in SCM. I'm ysing codium which also does Clippy dmart stuff trying to be helpful and breaks code. They keep pushing AI junk and break functionality to the point that I'm looking for another editor with usable muliple cursors (not *vim and not helix which breaks my vim muscle memory).

They broke it again today with release 1.107 which throwns a weird shadow when I resize the window in Gnome. Got fed up with it, so I pinned the package to 1.106.

If you like nvim you'd probably be interested in helix (https://helix-editor.com/) too

Copilot

Reply on news.ycombinator.com