Earlier quoted context omitted.
Use \b lol
That doesn't work in Vim. Or rather: it matches the backspace character, which isn't what you want.
Damn. My apologies, then.
Leaving Neovim for Zed
61–70 of 331 posts
Re: Leaving Neovim for Zed
#62Most 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 completely antithetical to the slim, minimal philosophy of vim.
At least the original vim is still around, and the js kids are allergic to parens so there's an alternative.
Re: Leaving Neovim for Zed
#63I 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 EMacs and LazyVim seem to have no problem with it. I couldn’t work beyond that point.
Re: Leaving Neovim for Zed
#64It was a great sales pitch until the Linux and Apple comparison.
I can't take seriously someone, who says that Apple's stuff runs smoother (unless we are talking about useless animations).
Re: Leaving Neovim for Zed
#65Honestly, 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??
Re: Leaving Neovim for Zed
#66I’m actually in the opposite camp, I had left VSCode for Zed about 6 months ago and used it exclusively at work/personal projects. I’ve customized it extensively, and loved its approach to Vim integration. But in the last two weeks I’ve made the switch to Neovim (using a customized LazyVim [0] setup). I really like Zed but as others have pointed out they are not prioritizing features around REPL’s, AI, and collaborat…
Big fan of LazyVim here. The default config does everything I need it to do.
Re: Leaving Neovim for Zed
#67I 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.
To paraphrase an old quote, "every new text editor grows until it is bloated with collaboration and AI features." Thank god we still have vim and Emacs.
Emacs[1] has been bloated with collaboration (gnus, etc) and AI features (doctor, lisp in general) for decades!
[1] Eight Megabytes and Constantly Swapping
Re: Leaving Neovim for Zed
#68I 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
Re: Leaving Neovim for Zed
#69I tried out Zed and really like it, but its still lacking things like EditorConfig support, so project switching sucks. Has strong potential to replace vscode entirely if they don't get carried away with fancy features
Re: Leaving Neovim for Zed
#70I’m going to somehow misuse this discussion to ask for the readership help about something: I don’t understand the appeal of VSCode or more exactly I don’t understand the appeal of the text editor propped with plugins to be a semi-IDE so I guess that would also include Neovim with plugins. In my career, I have used text editors including vim which I still very much enjoy and both Eclipse and IntelliJ when I used to c…
One answer may be that it’s not that slow for everyone. It could vary with the kind of computer you’re running it on, or what languages you’re using it for, or the size of the codebases.
I’ve seen people complain all the time about how slow VS Code is, and I haven’t really had that issue on an M1 Mac, at least not since some major perf work in VS Code a few years ago. And I know what a fast editor is — I’ve used Helix and minimally-configured Neovim for years.