I tried and I really liked so I considered a switch but:
- It's missing debugging capabilities. They have it in their pipeline, but, as it stands, not for production use if you do not want to develop with debug prints all the time.
- The font rendering still needs some polishing. On a non retina display using a dark mode in mac the fonts are pretty blurry in comparison to vscode, and I had to use a medium weight for the editor font for improved readability.
i'm fairly surprised that i fired it up, wrote some go code, and the lsp worked.
I too am growing tired of tinkering and want minimal configs. So much so that I had to force myself to stop using doom emacs in favor of neovim. Neovim setup is much simpler now that lua exists but i'd rather not tinker as much as I do.
Enabling/Disabling plugins is fun in a way when you wanna take the time to do that.
I might give zed a spin a few more times.
Can zed be run from a terminal over ssh or is it just GUI?
It’s only GUI, but you can have it perform the edits over SSH. So it appears to be all local for you, but the files are actually modified on the remote host.
This is the part that impressed me the most! I know other editors "support" this kind of workflow, but opening "remote projects" via SSH is so clean and intuitive in Zed! I love that when you pop the terminal open on a "remote" Zed window, it just opens right in your remote host directory where you would expect.
> my workflow consists of switching back and forth between a terminal window and an editor window.
Same! I run neovim in tmux together with stuff I hack on. I switch beteen tmux windows with shift-arrows and it works so well. I run this full screen in Ghostty. No distractions.
I try Zed and VSCode and I always come back to this setup. It works so well for me personally.
Yeah the tmux / vim combo is so hard for me to beat with other editors still. I used Zed exclusively last month thinking the LLM integrations would be a compelling enough reason to finally switch. Like the post author, I'm a little fatigued with config / plugin churn since I switch languages frequently and it always takes some customizing to make vim work well when I do that.
As the author describes though, I found myself copy-pasting a lot between LLM chat and editing buffers. In tmux, I have a really simple function that copies select panes (using tmux capture-pane) into my prompt, or I can give it full files for context. Most of the time though, I can do something like `llm -t 0 -t 1 'what is this libSSL error indicating? here's my code', where -t 0 gives it my vim pane and -t 1 gives it the terminal I'm running things in. I've been surprised that this somewhat rudimentary approach has felt far more effective than the more sophisticated editors I've been trying.
Is this just me? Does it seem to others that the LLM-enabled editors coming out these days still require a lot of copy-pasting of context that can be easily provided with just a dump of tmux output?
Everything-is-just-text might be crude but dang does it make quick and dirty LLM integrations a snap!
I use tmux and neovim along with the copilot plugin[0]. I prefer it over the VSCode copilot integration, to me it feels less obtrusive and out of the way, which is what I want. You're also not dealing with API costs since it uses the regular Copilot subscription.
> I try Zed and VSCode and I always come back to this setup.
I have Ctrl+` set to switch focus between the editor and the terminal panes in VSCode, so I can toggle between them pretty easily as this is also my workflow
If anyone's wondering, here's what I have in my keybindings.json
ctr+` is the default behavior on VS Code I use it all the time and I didn’t set it up and I’m sure as hell neither did my co workers.
It’s a nice short cut if you have a keyboard with backtick to the left of 1 in the numeral row. If you’re from a country where keyboards have a different key there, I would recommend setting up a short cut manually.
Nope. It minimizes the terminal by default, at least on macOS. These keybinds leave the terminal / lower bar open and just shift focus back to the editor.
I’ve definitely done the ^Z thing. The catch is to remember you did it if you get distracted in the terminal. Nothing like finding some vim job in the background and you can’t remember what it was.
For me it only works because I never reuse a single terminal for unrelated things. Additionally, I have my virtual desktops grid set up so that different types of tasks are always in certain places, so if the switcher shows a terminal somewhere, I know roughly what it's for even without going to look at it. So I can't "lose" a terminal.
So it's fine for X11 terminals, but not for /dev/tty2
Don't forget you can just :!some-shell-command though - not just in vim but in lots of programs even.
What editor state are you losing when you leave vim?
I run a pretty light vanilla vimrc (60 lines maybe) and with two lines you can enable vim undofiles and returning the cursor to the last location upom reopening a file. For me, quitting vim is functionally equivalent to ^Z?
That's true for me too but usually my tabs and windows are managed one level higher, by the terminal emulator, or I'm opening vim with -o/-O to open a split window directly.
I don't use tabs, sometimes I use split windows (usually only when vim-diffing), mostly I use multiple terminal windows in a tiling WM. I do use multiple buffers but I usually don't care about editing more than one or two at a time and it's easy to re-open these whenever I need to.
You may lose LSP state like rust-analyzer's which takes a while to restore. You may lose opened buffers and positions within them (unless you have some session restore logic which may also take time), window layout, copy buffers, edit history and lots of other state.
Retaining positions, buffers, and edit history between sessions is all straightforward in vanilla vim though. Unless you run an autolinter or formatter that edits your target file and wipes the history.
Another (neo)vim+tmuxer chiming in. One major missing feature (compared to vscode) is opening file links from the terminal back in vim. It was such a major pain to me, so I ended up writing a tmux plugin to solve it. I thought you might find it useful - https://github.com/artemave/tmux_super_fingers
That's the one reason I actually did end up using vim, even if Gui editors are theoretically highly superior.
It's always there in the terminal with me. So you know how it goes, you set up $awesome_ide on a separate screen or what have you; start messing in the terminal, and then for quick edits you grab vim anyway. And once you have the whole edit/test/edit/test loop going, well, vim is still there. And hours later you find out the whole IDE has just been sitting there the whole time.
So yeah, I'm not married to vim I don't think. A nicer terminal editor would always be welcome? And if it has vi(m) bindings to ease me into it? Who knows.
Not being in the terminal is a feature, not a bug imo. Terminal editors just can't compete with the GUI, so their only viable role is as an editor of last resort on systems where you don't have a GUI.
The tab completion for the AI suggestions is 100% the most annoying feature I've ever used. I just want to indent my line and not have to keep hitting escape 1000 times. Awful.
I’ve been using Sublime Text for more than a decade and I gave Zed a try recently. I don’t have good reasons like the author, but I kinda wanted to see what the hype was about.
I really liked everything about it including the much better LSP support and the base key map for Sublime Text was very close so I felt at home quickly.
Then I tried actually writing code in my usual workflow and this is where things started to fall apart. I’ve been writing in Ruby for almost 10 years now and when I type things like `def<tab>` I’m used to Sublime filling in the snippet and allowing me to quickly enter and tab through the components. Same for a bunch of really common Ruby concepts like blocks. I found this to be very limited and even though I created custom snippets they never would render with the correct indentation. I think the Ruby language extension just needs some additional work and probably doesn’t get much attention. For me I didn’t have time to figure it out and contribute so I went back to Sublime Text.
I will definitely continue to play with Zed and see if it gets better because of the native AI integration. I’m not an AI fanboi and I usually avoid it, but being able to supply the open and existing files as context when asking the assistant to generate things like tests performed much better with context than without and were much closer to how we write and format tests.
This is close to my experience. Also long-time Sublime user, almost always writing Ruby.
I don't know if I'm an AI fanboi or not, but for generating things like factorygirl definitions and simple rspec unit tests, GPT is seriously good (in the sense that it saves me tedious work, not that it is particularly fantastic).
I just can't see myself ever leaving Sublime. VS Code is good, but uses way too many resources without really delivering commensurate functionality compared to Sublime. I thought Zed might do it, but their main focus seems to be trying to integrate LLMs which are a productivity drain with how inconsistent they are. So if anything that's a reason to stay away, not to use it. Thus far Sublime is the only editor which is just focusing on doing a good job being an editor and not using hella resources.
I echo this sentiment. Also, a long time rubyist. I pretty much go between neovim or Sublime everything else has felt off for Ruby development. I use vintage (vim) mode for Sublime and it’s the sweet spot. I get all the motions, but also some -non vim actions that I appreciate. This might feel like uncanny valley, but it works.
I’ve fully migrated from Sublime Text to Zed, but in these areas both are lacking things the other has.
Sublime has great language support out of the box but poor LSP support (basically outsourcing it to a user plugin instead of having a native integration).
Zed has great LSP support but ”poor” language integration (also outsourcing the language plugins to the community, which makes the vary in quality and feature set).
But Zed has great AI integration which Sublime completely lacks, if you’re into that.
I use cursor and vim now. I have been on vim for 15+ years. Are there LLM extensions that make vim work like all these new AI editors? I would prefer to stay in 100% vim world, but the productivity benefits from LLMs with composer mode and context is so powerful.
dingllm is very straightforward, you submit your entire selection/buffer and it streams out to the current position. mine is a bit more complex with configurations, context management and so on.
The thing I always tell people is just roll your own. The docs are there, the LLM is there, use them. At the end of the day it's just an http call against text from your buffer to put text in a buffer.
I've been daily driving Zed on Windows (building from source) for maybe 2 months now and I'm pretty happy. It's a nice middle-ground between editing single files in NeoVim and bringing up a JetBrains IDE for an incredibly complex project.
I think the only thing that is really outstanding for Windows is SSH support.
Everything largely "just works" and my experience getting a plugin with syntax highlighting working and merged for a DSL I maintain was very smooth.
Zen feels so fast on my old intel MacBook it is crazy! I will move entirely to zed from vscode when they implement dynamic port forwarding in their SSH mode ( I feel like it is close )
I'm using Zed too. It is VS Code-ish but feels fast, works out of the box and feels just... right. I wish it had support for Jupyter notebooks, but it looks like it will get there.
And it never crashed on me, unlike VSCode which reminds me of Windows 3.1.
Yeah, notebook support for me is personally the biggest deal breaker right now. I feel pretty confident I could switch the day that notebook support matures.
They don't have syntax highlighting, Zed uses LSP server for each language. I'm sure lisps have them, the question is just to add support in Zed for a particular one.
I still prefer neovim+lazy, but Zed is really pretty good and way way way faster than VSCode. Really, my only stumbling block with Zed is simply that while its vim mode is pretty decent, it's not the same as my neovim+lazy setup. However as pointed out in TFA, it looks like the Zed folks are doubling down on the vim bindings:
For me the problem is that it takes several seconds for Zed to open a file from across the network. Mostly just small code files. They are instant when I open them with vim in the terminal. I open so many files that the delay becomes a slog.
I've been editing directly in the terminal for many years and was looking forward to moving back to a real desktop IDE, but I bounced right off of this. Does it not happen for you or it's just not that bad? Does anyone know of a solution?
Zed is the only GUI editor I've used as my daily driver after 15+ years of development (hardcore vim fan). Vim Mode is wonderful, the terminal pane works well, UI is butter-smooth, LSP integration beats VS Code's IMHO, and the LLM-powered autocomplete works well (haven't tried chat/generation). Nice themes, too.
The lack of debugger support will put some off, but I bet they'll get to it someday. It's already progressed so much in the four or five months I've used it (esp. Vim Mode).
I wanted to like Zed but tying buffers to tabs is a deal breaker for me. They have really good vim motion support but don't let you view any buffer in any pane.
As another neovim/vim expat using VSCode these days (because I got tired of fixing configuration), this is also my number one complaint. I want to be able to view any file in any split. Honestly, I wish my whole window manager worked this way (stacking WMs get close). And my browser - why can't I display any "tab" in any window with a couple of key strokes? It drives me batty how inflexible the split/buffer/pane/window model is outside of vim and emacs land. I don't want tab groups; I don't want independent windows; I don't want VSCode editor groups that are pita to close. For the love pixels, I want to make the content I care about appear in the window I have in front of me, where those windows are arranged to consume my monitor's space without overlap. /soapbox-dismount.
Not that guy but how about viewing two parts of the same file side by side, organizing them vertically or horizontally as needed, opening like a hundred files and cycling through them in a sane fashion, probably dealing with macros. Tabs get very annoying if you have too many of them, and buffers are a good solution to that problem.
Tried for a long while to use Zed. It was great and I loved it - and maybe I could have switched to a GUI editor for real though for the first time in my life.
But man. File trees and tabs are the worst DX I can possibly imagine. Try as I might, I just could not get used to the tab and tree workflow. Creating new files killed me. Hiding the tab didn’t really help because the editor assumes you’re using tabs and at that point it doesn’t feel like buffers, it feels like tabs with the tab bar hidden (go figure).
I’m not even a buffer power users, but I think the default assumption of buffers over tabs, and explore over a file tree, led to 1000 other great decisions that make vim vim.
I think unless the zed core team really tried to move away from tabs and trees (and I don’t think they would nor should) they’ll fail to capture a meaningful share of vim users
I will never understand how you go back from a very customized editor setup to the one with "reasonable defaults with little to no things to configure".
>I will never understand how you go back from a very customized editor setup
because when the very customized setup inevitably breaks the amount of headache you have is roughly proportionate to the amount of customization, whereas software with strong defaults tends to deal with that for you.
This is particularly the case with neovim which, in almost deliberate defiance of any systems thinking, just tends to consist of a few dozen moving parts loosely tied together and you have to sort of pray that updating some doesn't just break things. Paraphrasing Russ Ackhoff, if you take the best part of every car and put it together you don't get the best car, you get something that doesn't even drive, this is how I've felt more than once with very bespoke editor setups
Haha this is so true. I stopped upgrading neovim when something little broke and I couldn't work out how to fix it an hour or so. It was something stupid like the column bar not having the right colour anymore.
Yeah, they changed the default colorscheme in neovim at some point in the last year or so. I have an extremely minimal
config and don't even use syntax highlighting or tab completions but I could not get it to render the way it used to. I wasted at least 30 minutes on this for absolutely no good reason. So I git bisected, made my own build (which took maybe 10-15 minutes) and will likely never upgrade neovim again.
I see people mentioning neovim "breaking" and to this day I have no idea what everyone is talking about. I have a very customized neovim setup, update almost every day, and quite literally have never experienced a single thing breaking.
I agree. Cramming a dozen of low quality plugins without understanding how they operate and hoping updating won't break things is not a great way to go.
I understand "just make it work" mentality, but it might be useful to have deeper understanding of a tool you use several hours everyday.
Back in the '90s I would customize my development environment to within an inch of its life, but after going from one machine to the next, one toolchain to the next, one operating system to the next, year after year, culminating in one ridiculous six-month period when I had to pave my dev machine and reinstall everything from scratch every two weeks (yes, this was stupid; yes, I knew it was stupid at the time; no, I had no way out of it, not if I wanted to keep my job) - I learned that adapting myself to the defaults was a lot less work than adapting the settings to me.
Or, to put it another way: every step you take away from the mainstream has a cost, so you had better know how much you are willing to pay and budget your quirks accordingly.
How is the work of copying an editor config/plugin folder with a script every two weeks for six months worse than using the bad suboptimal defaults every day?
> every step you take away from the mainstream has a cost
If it can open text files and has a cursor im good. Irl i dont grow attached to environments either. Its just to expensive when they vanish. Its just people now :)
I just think ok how spoiled we are. In the 50-60s the typist diploma required 300 strokes per minute, without typos, on a mechanical typewriter, from paper or dictation. I never had to tape up a smashed finger.
Or you just had to structure your knowledge bases and settings properly. I can restore dev-part of my pc anytime by installing git and making a few clones. Going to another machine is literally a matter of pasting gitlab credentials and init scripts into a terminal. I can even replay things if they have to repeat in a project because I save all the steps I take into a project/job-wise obtf.txt. Working in a non-automated non-repeatable way is so self-inflicted. It’s akin to not having a car because it has a cost.
> I will never understand how you go back from a very customized editor setup to the one with "reasonable defaults with little to no things to configure".
That's one of the reasons why I chose Vim over Emacs after switching back and forth for a while.
I do prefer the design of Emacs because I prefer having full control over my environment - I even coded more than a couple of tiny, application-specific editors - but sometimes I have better things to do than e.g. reading docs or searching for a plugin/extension mod that does what I need, or do it myself; sometimes I am a mere luser who want things to "just work" out-of-the-box.
>I love (Neo)Vim. Like I wrote earlier, it's been my primary editor for the past 15 years. What I don't love is all the configuration that goes into it before I can use it to start writing code.
this resonates with me. i've spent so much time configuring neovim in the terminal (kitty) and i've never had everything work 100% of the time. simple things just like seeing an entire typescript error are challenging to get working. those errors just continue on one line outside of the screen.
with LLM's the tradeoff tipped in the favor of cursor with the neovim extension.
> 2. It just works
so i switched to cursor last week from neovim in the terminal and this is how i feel. but, i'm not going to invest more time to check out Zed now that i just got cursor set up the way i like it.
but it's great to see all the progress in IDE's lately.
I switched from VSCode to Zed and I’m a huge fan! They don’t have support for Jupyter notebooks yet so I have to use Spyder for those but I love how easily Zed runs and how configurable it is.
Also half my workspaces are on remote servers and Zed lets me switch between remote and local workspaces easy which I appreciate.
VSCode is currently more complete than Zed but Zed is more configurable. Also I suspect that Zed will improve rapidly and VSCode is mostly already plateaued due to Zed being new and open source and VSCode being old and made by Microsoft.
153 comments
[ 2.1 ms ] story [ 219 ms ] threadI too am growing tired of tinkering and want minimal configs. So much so that I had to force myself to stop using doom emacs in favor of neovim. Neovim setup is much simpler now that lua exists but i'd rather not tinker as much as I do.
Enabling/Disabling plugins is fun in a way when you wanna take the time to do that.
I might give zed a spin a few more times.
Can zed be run from a terminal over ssh or is it just GUI?
https://zed.dev/blog/remote-development
Same! I run neovim in tmux together with stuff I hack on. I switch beteen tmux windows with shift-arrows and it works so well. I run this full screen in Ghostty. No distractions.
I try Zed and VSCode and I always come back to this setup. It works so well for me personally.
As the author describes though, I found myself copy-pasting a lot between LLM chat and editing buffers. In tmux, I have a really simple function that copies select panes (using tmux capture-pane) into my prompt, or I can give it full files for context. Most of the time though, I can do something like `llm -t 0 -t 1 'what is this libSSL error indicating? here's my code', where -t 0 gives it my vim pane and -t 1 gives it the terminal I'm running things in. I've been surprised that this somewhat rudimentary approach has felt far more effective than the more sophisticated editors I've been trying.
Is this just me? Does it seem to others that the LLM-enabled editors coming out these days still require a lot of copy-pasting of context that can be easily provided with just a dump of tmux output?
Everything-is-just-text might be crude but dang does it make quick and dirty LLM integrations a snap!
[0] https://github.com/github/copilot.vim
I have Ctrl+` set to switch focus between the editor and the terminal panes in VSCode, so I can toggle between them pretty easily as this is also my workflow
If anyone's wondering, here's what I have in my keybindings.json
It’s a nice short cut if you have a keyboard with backtick to the left of 1 in the numeral row. If you’re from a country where keyboards have a different key there, I would recommend setting up a short cut manually.
I know people who use ^Z to suspend vim and then foreground it again.
So it's fine for X11 terminals, but not for /dev/tty2
Don't forget you can just :!some-shell-command though - not just in vim but in lots of programs even.
You don't mind losing all your editor state? If you don't like working with multiple terminal windows, why not open a term within vim with `:term`?
I run a pretty light vanilla vimrc (60 lines maybe) and with two lines you can enable vim undofiles and returning the cursor to the last location upom reopening a file. For me, quitting vim is functionally equivalent to ^Z?
Retaining positions, buffers, and edit history between sessions is all straightforward in vanilla vim though. Unless you run an autolinter or formatter that edits your target file and wipes the history.
I don't use any other LSPs which have a long warmup time, but if I did then they can also be used behind ra-multiplex.
In my configuration vim will save (among other things):
- Cursor position
- Undo history
- Register state
:term is clunky for me, mainly because my muscle memory is to just :wq
I got it working as seamlessly as I could once just in an attempt to use it but I stopped pretty quickly.
That's the one reason I actually did end up using vim, even if Gui editors are theoretically highly superior.
It's always there in the terminal with me. So you know how it goes, you set up $awesome_ide on a separate screen or what have you; start messing in the terminal, and then for quick edits you grab vim anyway. And once you have the whole edit/test/edit/test loop going, well, vim is still there. And hours later you find out the whole IDE has just been sitting there the whole time.
So yeah, I'm not married to vim I don't think. A nicer terminal editor would always be welcome? And if it has vi(m) bindings to ease me into it? Who knows.
https://helix-editor.com/
It's a terminal editor with mouse support and sane key bindings.
I really liked everything about it including the much better LSP support and the base key map for Sublime Text was very close so I felt at home quickly.
Then I tried actually writing code in my usual workflow and this is where things started to fall apart. I’ve been writing in Ruby for almost 10 years now and when I type things like `def<tab>` I’m used to Sublime filling in the snippet and allowing me to quickly enter and tab through the components. Same for a bunch of really common Ruby concepts like blocks. I found this to be very limited and even though I created custom snippets they never would render with the correct indentation. I think the Ruby language extension just needs some additional work and probably doesn’t get much attention. For me I didn’t have time to figure it out and contribute so I went back to Sublime Text.
I will definitely continue to play with Zed and see if it gets better because of the native AI integration. I’m not an AI fanboi and I usually avoid it, but being able to supply the open and existing files as context when asking the assistant to generate things like tests performed much better with context than without and were much closer to how we write and format tests.
I don't know if I'm an AI fanboi or not, but for generating things like factorygirl definitions and simple rspec unit tests, GPT is seriously good (in the sense that it saves me tedious work, not that it is particularly fantastic).
Sublime has great language support out of the box but poor LSP support (basically outsourcing it to a user plugin instead of having a native integration).
Zed has great LSP support but ”poor” language integration (also outsourcing the language plugins to the community, which makes the vary in quality and feature set).
But Zed has great AI integration which Sublime completely lacks, if you’re into that.
https://github.com/yetone/avante.nvim
https://github.com/baketnk/l.nvim (self-shill, docs overhaul needed)
which was inspired by the original:
https://github.com/yacineMTB/dingllm.nvim
Also brand new from ggerganov: https://github.com/ggml-org/llama.vim
dingllm is very straightforward, you submit your entire selection/buffer and it streams out to the current position. mine is a bit more complex with configurations, context management and so on.
The thing I always tell people is just roll your own. The docs are there, the LLM is there, use them. At the end of the day it's just an http call against text from your buffer to put text in a buffer.
https://www.cursor.com/
I think the only thing that is really outstanding for Windows is SSH support.
Everything largely "just works" and my experience getting a plugin with syntax highlighting working and merged for a DSL I maintain was very smooth.
And it never crashed on me, unlike VSCode which reminds me of Windows 3.1.
https://zed.dev/blog/vim-2025
It's be kinda cool if Zed had a TUI mode (in that the rendering engine would generate VT escape sequences).
I've been editing directly in the terminal for many years and was looking forward to moving back to a real desktop IDE, but I bounced right off of this. Does it not happen for you or it's just not that bad? Does anyone know of a solution?
The lack of debugger support will put some off, but I bet they'll get to it someday. It's already progressed so much in the four or five months I've used it (esp. Vim Mode).
But man. File trees and tabs are the worst DX I can possibly imagine. Try as I might, I just could not get used to the tab and tree workflow. Creating new files killed me. Hiding the tab didn’t really help because the editor assumes you’re using tabs and at that point it doesn’t feel like buffers, it feels like tabs with the tab bar hidden (go figure).
I’m not even a buffer power users, but I think the default assumption of buffers over tabs, and explore over a file tree, led to 1000 other great decisions that make vim vim.
I think unless the zed core team really tried to move away from tabs and trees (and I don’t think they would nor should) they’ll fail to capture a meaningful share of vim users
I will never understand how you go back from a very customized editor setup to the one with "reasonable defaults with little to no things to configure".
Great talk on this topic by TJ: Personal Development Environment: https://youtu.be/QMVIJhC9Veg
because when the very customized setup inevitably breaks the amount of headache you have is roughly proportionate to the amount of customization, whereas software with strong defaults tends to deal with that for you.
This is particularly the case with neovim which, in almost deliberate defiance of any systems thinking, just tends to consist of a few dozen moving parts loosely tied together and you have to sort of pray that updating some doesn't just break things. Paraphrasing Russ Ackhoff, if you take the best part of every car and put it together you don't get the best car, you get something that doesn't even drive, this is how I've felt more than once with very bespoke editor setups
Just hope that nothing breaks in an OS upgrade.
I understand "just make it work" mentality, but it might be useful to have deeper understanding of a tool you use several hours everyday.
Or, to put it another way: every step you take away from the mainstream has a cost, so you had better know how much you are willing to pay and budget your quirks accordingly.
> every step you take away from the mainstream has a cost
Customizing neovim is mainstream
That's one of the reasons why I chose Vim over Emacs after switching back and forth for a while.
I do prefer the design of Emacs because I prefer having full control over my environment - I even coded more than a couple of tiny, application-specific editors - but sometimes I have better things to do than e.g. reading docs or searching for a plugin/extension mod that does what I need, or do it myself; sometimes I am a mere luser who want things to "just work" out-of-the-box.
this resonates with me. i've spent so much time configuring neovim in the terminal (kitty) and i've never had everything work 100% of the time. simple things just like seeing an entire typescript error are challenging to get working. those errors just continue on one line outside of the screen.
with LLM's the tradeoff tipped in the favor of cursor with the neovim extension.
> 2. It just works
so i switched to cursor last week from neovim in the terminal and this is how i feel. but, i'm not going to invest more time to check out Zed now that i just got cursor set up the way i like it.
but it's great to see all the progress in IDE's lately.
Also half my workspaces are on remote servers and Zed lets me switch between remote and local workspaces easy which I appreciate.
What drew you to Zed over VS Code?
Also I’m not immune to hype I suppose
I switched just to keep things interesting and didn't go back. That was last year maybe Sep/Oct.
I had to use VSCode to collaborate and like it in general.