Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Leaving Neovim for Zed

stevedylan.dev

Post reply on HN
Print view View original

131–140 of 331 posts

Re: Leaving Neovim for Zed

#131

Post by danielvaughn »

Voklen wrote: post #109

For me this feels similar to why I use Helix[1]. I used to use VSCodium and had tried to switch to Vim or Neovim multiple times but didn't manage because of all the plugin configuration to be able to program. Then I saw an HN post about Helix, started it up and it just worked and so haven't used anything else since. I find the Helix keybindings easier to learn because you see what text will be affected by any operati…

I also heard about Helix and have been curious about it, for the same reason. If I’m going to learn Vim keybindings, it’s because I want to move fast. Tweaking configuration files for an evening is the exact opposite of moving fast.

Re: Leaving Neovim for Zed

#132

Post by riwsky »

icar wrote: post #103

"It just works" is precisely why I use Jetbrains products. I'm amazed they are not that common in many developer communities. They are amazing tools.

The support for remote or in-docker development has been an issue, personally. Terminal editors and VSCode are much more “it just works” in this regard, especially when joining codebases that used docker to isolate all the dependencies to actually run tests/services for local dev.

Re: Leaving Neovim for Zed

#133

Post by nsonha »

I have started using Zed as the secondary editor, after VSCode, since they added the repl feature, which is based on Jupyter. It's not that it's a killer feature but that and AI, out of the box, and the cleaner UI attracted me.

That said I actually been using Cursor more in my testing of AI code because they just have better AI (with regard to how they add things into the context, I use both with sonnet). Also the UI integration is more comprehensive.

Re: Leaving Neovim for Zed

#134

Post by jdeaton »

Voklen wrote: post #109

For me this feels similar to why I use Helix[1]. I used to use VSCodium and had tried to switch to Vim or Neovim multiple times but didn't manage because of all the plugin configuration to be able to program. Then I saw an HN post about Helix, started it up and it just worked and so haven't used anything else since. I find the Helix keybindings easier to learn because you see what text will be affected by any operati…

Helix has been trying to implement a plugins system for like 2 years that should tell you everything you need to know about its future prospects

Re: Leaving Neovim for Zed

#135

Post by beginnings »

LtdJorge wrote: post #127
kvark wrote: post #108

Earlier quoted context omitted.

Personally, it’s because they are not open source and not as fast.

Yesterday RustRover became so unresponsive that the UI would freeze for more than 15 seconds (as reported by their exception notifications) and completions would take 5 seconds to appear and be wrong or lacking most times. I was seriously doubting the internal Rust engine (they don’t use rust-analyzer or LSP), so I switched to VSCode with the rust-analyzer extension, and the same happened there too, although no freez…

Rust Rover is terrible, they made it free and I still dont use it, Zed is great for Rust.

Re: Leaving Neovim for Zed

#136

Post by ilrwbwrkhv »

alberth wrote: post #12

I initially loved Zed. But as their focus has shifted to building Collaboration & AI features, and still haven’t yet nailed just being a good/great base editor, its become less useful to me. I still have a lot of hope for Zed. But for the time being, I’ve switched back to my old editor & IDE … and I’ll try Zed again at a much later date.

Zed also hastily went to v1. Simple things are missing such as labels to identify where a conpletion It's coming from when there are multiple completions with the same name. Also typescript types which are updated by an external process do not reflect unlike vscode.

They are now trying to do collaboration with ai to return money to investors but again nobody wants this.

That's why most editing tools should be open source and done by people passionate about it. The only company that managed to do paid editoes well is Jetbrains because their IDEs are actually much much better than the competition and much better than Zed.

Re: Leaving Neovim for Zed

#137

Post by adv_zxy »

phatskat wrote: post #105
irusensei wrote: post #25

I tried leaving vim for Helix but turns out it's not curated at my employer's site so I'm back to using vim. Zed would be even worse considering it's a desktop app. There is the option of using vscode but I'm one of those aliens who absolutely dislike that program.

I’m with you on VSCode, I just can’t get into it. 20+ years of vim does mean there’s a lot of muscle memory I’m not willing to put aside, and last I checked (admittedly years ago), the vim plugin for VSCode was meh

Maybe you can give the neovim plugin for vscode a try. As a long time vim/neovim user who occasionally do some C# modding stuffs in vscode I find it one of the best "vim" mode plugin out there. The fact that it spawns a real neovim instance makes it working great with your existing neovim config, no need to learn how to add your custom other-than-default vim keymaps using some json config files, it just works, even for navigation plugin like leap.nvim (if my memory is correct).

Zed seems to be using its own vim emulation and config syntax is a huge caveat to me.

Re: Leaving Neovim for Zed

#138

Post by zie »

riz_ wrote: post #7

I'm wondering if the author ever tried one of the many neovim distributions, which solve a lot of the problem they're describing. All of the plugins and integrations necessary are already set up to create a nice fully featured IDE-style environment. E.g. LazyVim, AstroVim or NvChad

There is also spacevim, which is what I use for remotes when remoting with Zed breaks(which is still quite often at the moment).

Re: Leaving Neovim for Zed

#139

Post by beginnings »

phatskat wrote: post #106
beginnings wrote: post #23

I started using Zed in the last month and I had a feeling it would end up taking a lot of Neovim users. Neovim gets a lot of users who need better performance than VSCode, like me, but the config is such a pain and there was a gap in the market for a blazingly fast GUI editor which Zed looks like filling. Supermaven still has some issues on Zed, but apart from that its been rock solid and ive fully switched from Neov…

If you ever go back to Neovim, I’ve had a lot of fun with NVChad. I still had to configure a little bit for LSP but that’s part of the ethos - sane defaults and most stuff off by default for performance and to reduce clutter.

I have my Neovim setup the way I like it, the problem is every so often something breaks, and I have to dig back into the config and ive completely forgot how everything works. Theres just a complexity with neovim config that id rather not deal with, its a bad DX in this day and age.

Re: Leaving Neovim for Zed

#140

Post by shmerl »

sph wrote: post #62
jgb1984 wrote: post #41

Most of the negatives mentioned (fragility, bugs, plugins breaking often) are specific to neovim. It's one of the reasons why I am and will always keep using vim instead of neovim. Vim is a much more mature ecosystem, less chasing the newest "plugin du jour", my vimrc is stable, based on a few dozen plugins which are feature complete and rock solid stable.

neovim is what happens when the javascript kids decide to "improve" one of the best editors ever created. The entire Lua ecosystem standing on 50 unstable plugins that provide the entire kitchen sink, yet do not even have a 1.0 version is nightmarish. Follow any guide and either everything breaks, or you get an hodgepodge of automagic popups, stuff that autodownloads, flash messages and useless features that are comp…

When I was looking for an editor that supported true color themes, neovim supported them, vim didn't. That decided what I was going to use. Stability is good, but if you need a feature that's not there - stability isn't helping.
Post reply on HN