[r4victor]

Hi, I'm the author of the post. I hope it resonates with many who got tired of VSCode and found Zed.

I'd also like to add there are many small features I miss in Zed that I don't go over in the post, e.g. autodetect and respect file's indentation (https://github.com/zed-industries/zed/issues/4681). But I see Zed is actively shipping the missing features, so I believe they'll improve significantly over the next year.

[delichon]

Your blog appears to have been hugged to death. I look forward to reading it someday.

[e12e]

https://archive.is/aaJh4

[SnowingXIV]

Have you tried using vim? Or rather nvim? If tinkering is your thing, feel free to completely do your own setup but out of the box lazyvim is pretty sane and you may not need much to get it to your liking.

But it’s very nice to easily able to extend or modify to fit your workflow. I’m just curious what people are getting out of zed that seems like vim has available.

[oneeyedpigeon]

I use both zed and vim, but the former for 'big' work because of:

a) file tree - I really like being able to 'root' the view at a directory, explore the hierarchy, and easily open any file within it

b) LSP - Zed's auto-formatting is it's best feature, for me

I generally like a whole bunch of things the gui gives me, but I would probably drop zed if I could get these two features working as well (or, at least, almost as well) in vi.

[pluies]

If it helps, I use the NERDTree plugin which gives a very decent file tree to vim.

[benji8000]

+1 for lazyvim. I tried multiple times to switch to nvim from vscode, but lazyvim finally made it painless. love lazygit too. debugging in nvim also works like a charm.

[SnowingXIV]

Yep, same experience (except Sublime with vim bindings) lazygit + lazydocker is really nice. Folke has done a great job.