Secondly, it was just one example that came to me from comparing this the other day. You could compile a long list of examples where Cursor gives better completions than Zed does.
I know that days of yak-shaving with LSP and emacs only gets me to a janky imitation of Visual Studio/XCode semantic search on my C++ work codebase. "Fuck it, let an LLM auto-complete based on vibes" has some appeal when you just get sick of trying to arm-wrestle clangd into ... whatever XCode or Visual Studio are doing to have functional semantic search across the project.
Although I have to say LLMs were a disaster at vibe-auto-completing in VSCode. So I mostly stick with semantic search in the IDE and editing in emacs like I always have.
It's human nature to start trusting AI suggestions just because they look good enough without actually checking them. That's going to lead to massive issues down the line the more it goes on.
Snippets are more useful.
If you're doing something repetitive, a vetted snippet does wonders. Learning how to make your own snippets with appropriate tab stops is a seriously underrated skill.
High competence in regex search-and-replace, multi-cursor, and snippets is an amazing combination.
But currently I sadly have to say the model's "help" is often a net negative.
An example is that when I have a module like Namespace::SuperAbcModule in a file at namespace/super_abc_module.rb and I rename the file to namespace/super_module.rb, Cursor will immediately suggest to change the module name to `Namespace::SuperModule`, Zed won't.
Also Cursor will suggest updates to lines throughout a file whereas Zed sometimes doesn't even look ahead 1-2 lines.
Having Claude Code and Codex built into the sidebar is hardly better than having them running in a terminal. I wish they'd invested all this time and effort improving the inline suggestions.