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

91–100 of 331 posts

Re: Leaving Neovim for Zed

#91

Post by mjoin »

adamors wrote: post #85
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.

Not sure what this fragility is. I’ve been using Neovim from the very first days, and it’s been stable throghout. Granted I have a 10+ year old vimrc and rarely add new plugins, but saying Neovim is fragile is nonsense. Don’t install every new plugin perhaps?

Same. Neovim and plugins I use have been remarkably stable from the start

Re: Leaving Neovim for Zed

#92

Post by Jenk »

metaltyphoon wrote: post #79
jack_pp wrote: post #36

Earlier quoted context omitted.

And then there's me that configs vim to use the system clipboard by default

Same. I can’t stand not having A clipboard for the entire OS

The `+` register is the system clipboard in vim already. What you're referring to is remapping the `+` register as the default register (in place of the 'unnamed' register, which is accessed explicitly as the `"` register) for some operations - typically yank and paste.

Re: Leaving Neovim for Zed

#94

Post by awongh »

twp wrote: post #11

If you want true Neovim in VSCode check out https://marketplace.visualstudio.com/items?itemName=asvetliakov.vscode-neovim You get a real, actual VIM (no half-assed bindings), and all the bells and whistles that come with VSCode.

I feel like using this extension is a little buggy. Especially around undo / redo actions being captured in “format on save” type actions that happen thanks to jslint or other tools.

Re: Leaving Neovim for Zed

#95

Post by skydhash »

sghiassy wrote: post #65

Honestly, I don’t understand when someone says VSCode is slow because it’s built on Electron. Are they talking about the 3 extra seconds on cold start? Is that really something to scoff at considering all its benefits??

For what it does, it’s slow. I used Jetbrains IDEs and I understand the slowness because of all the linting and indexing. But I bear with it because they are tailored to the language that they support and provide you with great utilities. VSCode tries to be the kitchen sink and it’s not great at either. And it’s not just code editing, every interaction with the interface feels slow. If I have 12 cores and 32 GB of ram, slowness for the same thing I was doing on codeblocks with a P4 and 1 GB of ram is the last thing I would accept.

Re: Leaving Neovim for Zed

#96

Post by nelsonfigueroa »

I like Zed too and use it on a daily basis. I've always wanted to take the opposite journey where I leave Zed/Sublime for Vim. While I have always to become a Vim expert, I never put in the time. There just hasn't been a situation in my career where I wish I could type faster than my thoughts. But maybe I'm just a scrub in this field.

Re: Leaving Neovim for Zed

#97

Post by tecoholic »

seabrookmx wrote: post #84
tecoholic wrote: post #63

I tried Zed just yesterday and sadly my experience wasn’t “just works”. It just works if you haven’t used any of the Neovim configs/distributions. But for someone who already uses LazyVim, LunarVim..etc., it’s kind of meeting the expectations. The issue for me was with the Docker LSP. I have a codebase where a Dockerfile is a Jinja Template. Zed’s syntax highlighting broke at the first curly braces. Both my Doom EMac…

Is it named Dockerfile or Dockerfile.jinja?

It’s named Dockerfile. However, I suspect if it’s named jinja, the Docker parts won’t be syntax highlighted!?!?

Re: Leaving Neovim for Zed

#98

Post by tecoholic »

magnio wrote: post #68
tecoholic wrote: post #63

I tried Zed just yesterday and sadly my experience wasn’t “just works”. It just works if you haven’t used any of the Neovim configs/distributions. But for someone who already uses LazyVim, LunarVim..etc., it’s kind of meeting the expectations. The issue for me was with the Docker LSP. I have a codebase where a Dockerfile is a Jinja Template. Zed’s syntax highlighting broke at the first curly braces. Both my Doom EMac…

> I have a codebase where a Dockerfile is a Jinja Template. Jesus

Trust me. I feel the same way.

Re: Leaving Neovim for Zed

#99

Post by christophilus »

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.

I use maybe 10 plugins. I update them whenever I update nvim which isn’t all that often. Rock solid.

Re: Leaving Neovim for Zed

#100

Post by jchw »

beginnings wrote: post #72
jchw wrote: post #60

Earlier quoted context omitted.

> On indentation, most files are going to be autoformatted by the LSP, and there are tab_size settings in the languages section, needing specific file settings seems like an edge case. Wow, absolutely not! Just so we're clear, when I say "per-file" settings, I don't mean in the configuration. I mean at runtime overriding the indentation settings for an open file. This is needed for many, many cases that I definitely…

They probably should have the option to change the tab size on an open file, but my point is, why wouldn't you have autoformatting on for YAML and JSON? You have a preference for indent size, and you want the same for every file, barring an edge case. "languages": { "JSON": { "tab_size": 4 }, "JSONC": { "tab_size": 4 }, "YAML": { "tab_size": 4 } } Edit: Yeah I see your point when you are not in control of the project…

To me it basically seems backwards. Of course I am not arguing against having a robust configuration for setting indentation settings, it's usually the ideal way to handle this sort of thing. However, it's ultimately still just a convenience feature; all you really need is the ability to set the indentation settings for the current buffer.

As far as editors that have automatic indentation features, Zed is definitely the first one I can think of where it had configuration for indentation settings per project/per language, but no ability to change it for the current buffer.

I'm sure in due time, it will probably gain most of these features as more people jump in and run into these problems.

Post reply on HN