A lot of editors are being discussed here but I see nobody has mentioned Kate (KDE's Advanced Text Editor) [1] in the conversation yet, so I'm doing it. Kate is a very mature and capable editor, and even if I only use it on Linux I'm glad to know that it is also available on macOS and Windows. It natively supports LSP and has much, much more to offer in terms of project management, support for build system, support f…
I use kate a lot when I need to inspect a huge file. Love the built-in rainbow rendering of columns for a CSV. Definitely a solid editor considering it is free and open source. I haven't done any serious dev with it though.
Leaving Neovim for Zed
301–310 of 331 posts
Re: Leaving Neovim for Zed
#302Re: Leaving Neovim for Zed
#303I tried emacs but found the same issue with plugins. It's just hard to keep up and organize them, so far lazyvim is the easiest for me but not "easy".
I'll have to try zed if it's foss. I do wish that some "standardized" plugins would just be integrated into the base application or a new application like Neovim from vim. I don't know the history, so I'm not sure how it came about, but it does feel like there is some stagnation with some of the gnu/linux stuff.
Re: Leaving Neovim for Zed
#304I’ve also recently switched (largely) from Vim to Zed and I also think that Zed is in many ways great. At the same time it’s been pretty frustrating to use an editor that is spending so much time building AI integrations, REPLs, and so fourth when basic things like cut and paste and common Vim motions still have so many bugs. I’d love to see them prioritize getting the basics solid first.
Yeah I feel the same way. The fact that Zed uses the system clipboard as the default register in vim mode, for instance, made it impossible to use in practice for me -- having every yank replace my clipboard was a bit of a nightmare!
Re: Leaving Neovim for Zed
#305There is one big issue with terminal editors that I keep running up against: single font size. One notable place where this is an issue is file listings, being able to have smaller proportional fonts makes a huge difference in usability. I have switched to Zed, but it sadly shares more in common with vscode than it does vim. I believe the ideal text editor would bring a small amount of GUI to the general idea of one…
People talk about not needing to type fast when coding, but I do need to navigate quickly, especially to not lose context while thinking. Ivy/Helm/Telescope with one of the various jump libraries (and LSP of course) makes code navigation feel second nature.
Re: Leaving Neovim for Zed
#306Echoing similar sentiments that I'm optimistic for Zed to become more polished and stable. Till then, Sublime Text 4 is still the best non-terminal text editor I've ever used and I continue to daily drive it. Sure its paid and non-FOSS, but its incredibly performant on Linux and Windows and its LSP extension + Sublime Merge fill the gap left by VSCode for me. Well worth the price tag IMO.
My only gripe with Sublime Text is that they've changed to a "semi subscription" license model, where licenses expire after 2-3 years, and you essentially need to buy it again after that time. It's essentially the same model used by other editors like the Jetbrains suite, but unlike Jetbrains, updates to Sublime Text (and Merge) are few and usually don't contain much other than bugfixes. I've faithfully purchased Sub…
Re: Leaving Neovim for Zed
#307Re: Leaving Neovim for Zed
#308> I was already a keyboard maximalist from previous jobs where I learned speed = productivity I've never understood this. In over 30 years in the industry, I've not once held a job where my keyboard speed had a noticeable effect on my productivity. Even when I had to type one-handed for a month, my productivity was unchanged. The average developer averages 10 lines of finished code per day. And even with a raw 10x th…
> The average developer averages 10 lines of finished code per day This is a ridiculous statement. Citation needed.
Re: Leaving Neovim for Zed
#309Earlier quoted context omitted.
I love IntelliJ, but VS Code has much better support for frontend technologies and TypeScript.
Until you work on a front end code base that's meaningfully large
I've worked on large front-end codebases. VS Code has much better TypeScript support than IntelliJ. I'd rather this not be the case because I much prefer IntelliJ.
Re: Leaving Neovim for Zed
#310Earlier quoted context omitted.
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
And, oddly, they chose to do their own Scheme implementation for it. Not that I'm against Scheme in particular, but a lot of other people justifiably seem to be. It doesn't have the speed or learn-it-in-10-minutes of Lua (nvim) or the historical excuse of Elisp/Vimscript (emacs/vim) or the ecosystem of Typescript (vscode). Strange choice.