I've been hitting that or something recent recently; it's what I would consider a severe bug because it can result in lost work and related. Basically, if you `git pull`, edit a file elsewhere, or use an LLM, zed's tree will remain stale unless you re-close and open the file. (Restarting the application doesn't sort it). So you end up overwriting the file with whatever was in the buffer.
There should be a concept called "engineering privilege".
I see some companies do things that are widely out of their core product and engineers there just having fun with a bunch of different stuff with seemingly no commitment to bring in revenue. They'll re-invent/re-write things constantly, write a new compiler/package manager for their chosen language, create new frameworks, new open source projects unrelated to their companies, etc.
It must be awesome to be able to work in these conditions and still get paid. I'm not hating on it, it's how we get a lot of the good stuff we use.
Their ACP integration is good (finally), at least with Codex. For when I want to be near the code, I prefer it now over TUIs or the Codex app. It feels much more immediate that way. Sticking to the basics will kill them IMO. They have been pitching themselves as agent-native for a while btw.
And the workflow they are describing in the post sounds amazing, I‘ve been wishing for that. It‘s orthogonal to CVS, no? You can still make PRs. But, crucially, you can loop people in early on, when it matters the most.
Unfortunately their Zed agent is completely broken when running on Windows connected to WSL/SSH remote because the terminal tool checks for paths using the local Path style (windows) which breaks when applied to paths on the remote (linux).
> Their ACP integration is good (finally), at least with Codex.
you must not use it much. try pasting in an image, quitting zed and restarting (ie: upgrading the app). it shows you the base64 encoded data instead of just showing the image. heck, it doesn't even show you the image when you paste it in. it just shows the filename.
ACP integration is very good, IMO. I'm using it with Claude Code. They've made so many improvements over time. I use image pasting myself, TBH I was excited it worked at all. Surprised that some rough edges around images are enough to ruin the whole thing for you.
images were just one glaring example... i didn't say anything about ruined, i just think a lot of those 'rough edges' are a bit more rough than they could be.
it is a code editor after all. how about integrating the LSP so that it doesn't have to resort to rg/grep/sed/scripts to edit code?
I agree with you that I wish they'd just nail the editor. I've been using it for years now and I really like it, but there are a few rough parts (settings and LSPs especially) that could probably be tuned up in no time if the focus was there.
Having said that, I love the idea of correlating the agent sessions to the changes. I'm glad someone is working on it.
You don't need a tool for that just configure your agent to write commit messages that link to a LLM log. And changes between commits. Maybe don't care why do we even care?
Of course you are right. I could write my own software to do what I want. Or, I could just do it all myself manually. This argument is valid in pretty much all cases, so I concede the point.
Did you even read the post? The idea is to tie conversations to code. This is a more sophisticated version of something like doltdb, not a git replacement.
Why develop this when the core editor is almost unusable? On Linux wayland, copypaste is broken, the file manager is laggy and snippets do not trigger before the heavy hint logic is done. This is just on top of my head, the list is long
"Almost unusable"? Slight hyperbole don't you think? I initially tried the Flatpak version on Fedora 44 and had a few minor problems, but since switching to the terra repos version (terrapkg.com) I've had zero issues, Have you tried that?
For me, its a massive improvement over IntelliJ for my daily workflow.
I can't use an editor where the file contents I'm being shown don't match the reality of the file. I guess this issue doesn't affect most people somehow, but in the age of CLI agents I'm not sure how more people aren't running into it.
I was really enjoying Zed for a short while before I ran into this fundamental issue.
All I can say is it's the only editor I've ever used with this type of issue and unfortunately it's a deal breaker for me. I can get by with any other editor even if they aren't my favorite, but only Zed made me realize that the most important thing an editor can do for me is accurately show me files.
Have you checked your fs.inotify.max_user_watches value? Maybe your value is too low and Zed can't watch the files that are changing. I know the JetBrains IDEs need the default to be increased on Linux because they detected it and prompted me to increase it.
Just installed it, works on my kde and niri setups (I logged out and switched to each), copy paste works as well. File manager laggi-ness I didn't notice I don't use it, I use it mostly to type stuff out.
I have never used snippets so unsure about that too, going from command bar seemed to work.
I think it might be bad, but could also be it's not correctly configured maybe try asking codex/claude or something to check if it can fix/fine tune the config, if that doesn't work file issues?
I do suspect it might be working for me cause I got lucky I do see an open issue[1], but given Zed is used a bunch the lack of comments does suggest maybe it's not that wide spread either way not a good look.
There are a lot of subtle bugs. I'm on macOS too, but perhaps my workflow is unusual? Every time I open it, I find small bugs. There are so many features that it's hard to maintain them, I guess.
For example, a lot of disable buttons do not actually disable stuff. They just hide it from the UI.
Agree, copy-paste feels like it works 80% of the time, which is maddening when 1 in 5 copy paste attempts fail. (mostly from zed to something else) Why??
At least Excel has the courtesy to telling you "Hey the copy-paste buffer said it didn't catch that, can you try again?"
I started using Zed a couple weeks ago and immediately had issues with copy/paste/buffer on an M1 Mac. I tried a few suggested fixes and they didn't work.
It still doesn't actually display a window my end until I press a keyboard key or move the mouse. So very often I sit and wait for it to open, only to realize I have to press a random key for it to unhide.
I have been using zed for almost 2ish years now, great overall, but last month when I tried ACP with opencode and even omp, it gave me many issues that it was easier just to use the terminal directly, oh, and I couldn’t select the model that time not sure if it’s fixed now.
I really love Zed and I want them to really succeed. Unfortunately it seems that they are swamped with various things and the issue tracker is not a priority for the team, which fair enough. OSS is a gift and I take it as such. Wild proposal but if someone is willing to start a "user advocate" contributor, I'll be happy to donate monthly so user requests can be taken a look at :)
This landing page is not good. It's mired in out-of-context jargon and implementation detail. (What does "virtualize the worktree" mean? Git already has "effectively free" branching. What does branching "mid-run" mean? How does a teammate "join while the work is happening"? What/where are they joining?).
What actually is it and what value do I get out of it?
Reading the linked blog posts: It's a layer on top of git for CRDT-based collaborative editing that captures addressable code deltas + agent conversations. I could have real-time collaborative humans + agents development and can resume any agent conversation from any point in history, because it is all stored (powered by DeltaDB). I guess?
I actually might want this, but wouldn't know it from the landing page.
Looks like a great feature/product/functionality. I hope that Zed editor will make it work with LLMs/agents that run in the terminal, not just the Zen Agent itself. Is it even possible? I use OMP.sh agent running in Zed terminal.
This is the killer Zed feature, IMO, that they support almost any agent via extensions. I deleted Cursor but still use the agent via Zed because it’s a lot nicer experience, Zed never had popups telling me Grok is half off. I also use OpenRouter and Zed.dev with it, that’s three providers out of dozens that it supports.
Exactly. The more competitive the space is, the more important it is that products purposefully support 3rd-party providers. Now that people are increasingly switching from Anthropic/OpenAI for inference reseellers and on-prem compute, transparency and portability will be the new values, not being slightly better than the next agent or model.
This feels very useful for training agents but almost completely useless to humans? Do I really want to go back to every change I made? Whatuse would that be?
Maybe I’m pessimistic, but I think this just gives micro-managers the data they need to micro-manage you. It invites people to scrutinize the process, instead of the results.
Not once have I wished to review a colleague’s conversation with an AI. I want to review finished work.
I look at this and I can only imagine layoffs being justified with “bad prompt quality”. An incident retrospective broadcasting your agent conversations to the entire company, with people speculating where you should have put the “make no mistakes”.
It’s a shame, really, because I like Zed as an editor, but I can’t bring myself to support them if this is the direction they’re choosing.
The sort of company that would do those things is going to be mandating you to use their enterprise AI plan anyway, which already lets them read all your conversations if they want to.
Letting them read my conversations is okay. Systematically reconstructing a timeline of every keystroke that went into a project, then immortalizing this timeline into a VCS, that’s the creepy part.
I suppose companies could do this anyway just by installing spyware in your work computer, but I would very much prefer if that spyware was not my editor of choice.
The way I’m seeing AI used by organizations is to produce process slop: tickets, summaries, docs, etc. rather than drive process change and optimization, or enable individuals to be more effective within the organization.
I had the great pleasure/misfortune of being forced to work with LaminDB, and I can tell you folks; data provenance isn't going away -- it will be used to train the very AI models snapping at our heels
i think a system that uses git and file system artifacts (txt/md/xml files whatever preference) is much better. eng teams need to define their artifacts, eg plan file, reqs etc whatever is needed and important to that team. the agent convo itself doesn’t add much value IMO and adds unnecessary bloat.
this looks like jetbrains "local changes" but globally synced. "for the agents" mights scare people who jump to think about micromanagers, but these people mostly hide or fake work. even micromanagers will eventually give you an agent to use so it won't matter what is in the change log, what matters is speed+quality. and since you can iterate from any branch you have inginite try and retry possibilities
Jujutsu already does this. I had agent screwing up changeset over couple hour long session and it took one shell command to split on pieces with longer pause.
The only downside is that because of Jujutsu snapshots it can't be used inside sandbox (since all jj commands are mutating)
This local history has saved my bacon on occasion. E.g. when I went too long without committing and something silly overwrote the file I was working on. Or because I did something silly with git. Then it is nice that there is still an independent backup elsewhere with different failure modes.
I really do like Zed, it's snappier than VS code and with pretty good vim emulation. Even through SSH, the native UI allows for no network latency, compared to something like vim+terminal. Like many other posters, I do feel like the core editor is getting worse.
Some issues I've encountered recently at work:
- Routinely encounter bugs with the python language server, it's particularly slow when compared to using VSCode. All that snappiest disappears when finding symbols after the '.' is considerably slower than my typing speed.
- I found similar issues with C++ code bases.
- It's also so hard to debug when something goes wrong. I was trying to find out why pyright keep spinning on startup, but the "LSP logs" never show anything.
- Connecting via SSH always opens the repo in restricted mode, even though I check the "Trust all projects in" checkbox. Never happened before.
- Debugger UI is a mess. Make a run, stop the run, edit the task.json, try running again, and 2 tasks show up. One for the old and one for the new.
--
I stuck with it because I really do like the UI, the performance, and initially it seemed to be an improvement from VS Code for my workflows, but lately I've been moving back to code as it seems more stable. I don't really use agent features, so I don't think I'm the target customer for this or other priority Zed features.
I do see the usefulness of something like this, I'm interested to see if the new agentic style of programming will result in the "code" part of editors becoming second class (for the better) and will allow for more rapid development. Although I'm not looking forward to read my coworker's "threads" of how a feature was made, I have a feeling that it will be more difficult to read than the raw code, as from my experience, LLMs don't really employ terse and effective communication (might not be entirely fair, I found ChatGPT /study mode pretty good.)
--
Anyone know of a good replacement editor that might meet my usecase? I'm really a batteries included type of developer.
Snapshots have an intention behind them as a chunk that the programmer thought of. It has infinite flexibility depending on the programmer/team. IMO they are a necessary feature, but the article considers it a bug. It’s an explicit and deliberate chunking of code writing process which is what you want in a chaotic “collaborative” environment. The system doesn’t get to decide but you decide when to commit.
Yes, it is open source, and I am not saying they should not do it. Chromium is also open source, but if they added too much nonsensical AI functionality, I would be upset. I am free to improve it on my own, but that does not mean I cannot express how I feel.
I have not gone to the Zed repository and created an issue telling them to stop developing DeltaDB because it takes away the maintainers’ time.
Zed should focus on basics. When it focuses on basics Zed is good.
https://github.com/zed-industries/zed/discussions/54150 failing to show newly created files and declining to provide a refresh button, instead adding a polling backend, breaks Zed on WSL.
Why a new version control system? Why not git, jj, or another existing system?
I've been hitting that or something recent recently; it's what I would consider a severe bug because it can result in lost work and related. Basically, if you `git pull`, edit a file elsewhere, or use an LLM, zed's tree will remain stale unless you re-close and open the file. (Restarting the application doesn't sort it). So you end up overwriting the file with whatever was in the buffer.
There should be a concept called "engineering privilege".
I see some companies do things that are widely out of their core product and engineers there just having fun with a bunch of different stuff with seemingly no commitment to bring in revenue. They'll re-invent/re-write things constantly, write a new compiler/package manager for their chosen language, create new frameworks, new open source projects unrelated to their companies, etc.
It must be awesome to be able to work in these conditions and still get paid. I'm not hating on it, it's how we get a lot of the good stuff we use.
This specific issue drove me mad for a couple of hours, I thought my LLM wasn't creating files and lying about it
Their ACP integration is good (finally), at least with Codex. For when I want to be near the code, I prefer it now over TUIs or the Codex app. It feels much more immediate that way. Sticking to the basics will kill them IMO. They have been pitching themselves as agent-native for a while btw.
And the workflow they are describing in the post sounds amazing, I‘ve been wishing for that. It‘s orthogonal to CVS, no? You can still make PRs. But, crucially, you can loop people in early on, when it matters the most.
Unfortunately their Zed agent is completely broken when running on Windows connected to WSL/SSH remote because the terminal tool checks for paths using the local Path style (windows) which breaks when applied to paths on the remote (linux).
I fixed this and a couple related issues in a PR but it hasn't gotten any attention yet. I guess they are a bit swamped. https://github.com/zed-industries/zed/pull/59937
> Their ACP integration is good (finally), at least with Codex.
you must not use it much. try pasting in an image, quitting zed and restarting (ie: upgrading the app). it shows you the base64 encoded data instead of just showing the image. heck, it doesn't even show you the image when you paste it in. it just shows the filename.
ACP integration is very good, IMO. I'm using it with Claude Code. They've made so many improvements over time. I use image pasting myself, TBH I was excited it worked at all. Surprised that some rough edges around images are enough to ruin the whole thing for you.
images were just one glaring example... i didn't say anything about ruined, i just think a lot of those 'rough edges' are a bit more rough than they could be.
it is a code editor after all. how about integrating the LSP so that it doesn't have to resort to rg/grep/sed/scripts to edit code?
I use it constantly but haven’t felt the need to paste an image yet. I guess I‘m using pi and the Codex app more for that.
sorry, i didn't mean a quantity of time, i meant depth of usage.
I agree with you that I wish they'd just nail the editor. I've been using it for years now and I really like it, but there are a few rough parts (settings and LSPs especially) that could probably be tuned up in no time if the focus was there.
Having said that, I love the idea of correlating the agent sessions to the changes. I'm glad someone is working on it.
You don't need a tool for that just configure your agent to write commit messages that link to a LLM log. And changes between commits. Maybe don't care why do we even care?
Of course you are right. I could write my own software to do what I want. Or, I could just do it all myself manually. This argument is valid in pretty much all cases, so I concede the point.
Did you even read the post? The idea is to tie conversations to code. This is a more sophisticated version of something like doltdb, not a git replacement.
So like Fossil then.
I like Fossil be because it can be all in one. WIki, a place to store architectural diagrams, tickets, basic webgui, etc.
Why develop this when the core editor is almost unusable? On Linux wayland, copypaste is broken, the file manager is laggy and snippets do not trigger before the heavy hint logic is done. This is just on top of my head, the list is long
"Almost unusable"? Slight hyperbole don't you think? I initially tried the Flatpak version on Fedora 44 and had a few minor problems, but since switching to the terra repos version (terrapkg.com) I've had zero issues, Have you tried that?
For me, its a massive improvement over IntelliJ for my daily workflow.
> massive improvement over IntelliJ for my daily workflow.
Why?
I used Zed for about 6 months but I lost motivation.
I have the full jetbrains subscription and use it for some debugging etc. I got vim for quick edits and cli tooling for ai. I got no use case for Zed.
I had to stop using Zed because of this issue (which persists despite being closed): https://github.com/zed-industries/zed/issues/38109
I can't use an editor where the file contents I'm being shown don't match the reality of the file. I guess this issue doesn't affect most people somehow, but in the age of CLI agents I'm not sure how more people aren't running into it.
I was really enjoying Zed for a short while before I ran into this fundamental issue.
I do not have this issue. (Yes, I am on Linux/Wayland)
All I can say is it's the only editor I've ever used with this type of issue and unfortunately it's a deal breaker for me. I can get by with any other editor even if they aren't my favorite, but only Zed made me realize that the most important thing an editor can do for me is accurately show me files.
Have you checked your fs.inotify.max_user_watches value? Maybe your value is too low and Zed can't watch the files that are changing. I know the JetBrains IDEs need the default to be increased on Linux because they detected it and prompted me to increase it.
Just installed it, works on my kde and niri setups (I logged out and switched to each), copy paste works as well. File manager laggi-ness I didn't notice I don't use it, I use it mostly to type stuff out.
I have never used snippets so unsure about that too, going from command bar seemed to work.
I think it might be bad, but could also be it's not correctly configured maybe try asking codex/claude or something to check if it can fix/fine tune the config, if that doesn't work file issues?
I do suspect it might be working for me cause I got lucky I do see an open issue[1], but given Zed is used a bunch the lack of comments does suggest maybe it's not that wide spread either way not a good look.
[1]: https://github.com/zed-industries/zed/issues/47004
Maybe I got lucky?? Does it not auto update on linux maybe I am on an old build... Very suspicious.
I use it as a daily driver with few if any problems, but I'm on macOS. Maybe their Linux support is particularly crappy?
There are a lot of subtle bugs. I'm on macOS too, but perhaps my workflow is unusual? Every time I open it, I find small bugs. There are so many features that it's hard to maintain them, I guess.
For example, a lot of disable buttons do not actually disable stuff. They just hide it from the UI.
Agree, copy-paste feels like it works 80% of the time, which is maddening when 1 in 5 copy paste attempts fail. (mostly from zed to something else) Why??
At least Excel has the courtesy to telling you "Hey the copy-paste buffer said it didn't catch that, can you try again?"
Linux Wayland (Ubuntu 26.04)
I started using Zed a couple weeks ago and immediately had issues with copy/paste/buffer on an M1 Mac. I tried a few suggested fixes and they didn't work.
It still doesn't actually display a window my end until I press a keyboard key or move the mouse. So very often I sit and wait for it to open, only to realize I have to press a random key for it to unhide.
Terrible Linux support.
why develop this when it seems jetbrains had a local history feature which recorded every change for the past decade(s)
> when the core editor is almost unusable
Shit, as someone who uses Zed everyday, I didn't realize what I am using is unusable.
Because it's not broken, the issues you're describing are far from universal. Also, fixing them won't bring any money.
Hmm, yeah before "DeltaDB" I have a big list of things I would rather they develop/fix:
- Vertical activity bar (https://github.com/zed-industries/zed/pull/58868#issuecommen... - rejected because it "doesn’t match our design vision for Zed")
This is my #1 annoyance: clicking microscopic icons at the very bottom of the screen to switch views.
- Don't crash my entire PC when there's a large (100+ MB) JSON file in the working directory
- Don't freeze when resuming from suspension (I suspect this is GPU-driver related on linux) forcing me to `killall zed-editor`
Sounds like a side-effect of being VC-backed. Like what the ex GitHub CEO went on to build (Entire). Unnecessary.
It also feels like his former company could implement his new company in a couple of weeks if they choose to.
A non-existent problem that nobody asked to solve...
I have been using zed for almost 2ish years now, great overall, but last month when I tried ACP with opencode and even omp, it gave me many issues that it was easier just to use the terminal directly, oh, and I couldn’t select the model that time not sure if it’s fixed now.
I really love Zed and I want them to really succeed. Unfortunately it seems that they are swamped with various things and the issue tracker is not a priority for the team, which fair enough. OSS is a gift and I take it as such. Wild proposal but if someone is willing to start a "user advocate" contributor, I'll be happy to donate monthly so user requests can be taken a look at :)
This landing page is not good. It's mired in out-of-context jargon and implementation detail. (What does "virtualize the worktree" mean? Git already has "effectively free" branching. What does branching "mid-run" mean? How does a teammate "join while the work is happening"? What/where are they joining?).
What actually is it and what value do I get out of it?
Reading the linked blog posts: It's a layer on top of git for CRDT-based collaborative editing that captures addressable code deltas + agent conversations. I could have real-time collaborative humans + agents development and can resume any agent conversation from any point in history, because it is all stored (powered by DeltaDB). I guess?
I actually might want this, but wouldn't know it from the landing page.
Looks like a great feature/product/functionality. I hope that Zed editor will make it work with LLMs/agents that run in the terminal, not just the Zen Agent itself. Is it even possible? I use OMP.sh agent running in Zed terminal.
It supports anything with ACP. So it can actually run Codex and Claude Code, not just the Zed Agent.
Looks like omp supports ACP, so all you have to do is specify a Custom Agent in Zed and it should just work.
https://omp.sh/docs/acp
https://zed.dev/docs/ai/external-agents
This is the killer Zed feature, IMO, that they support almost any agent via extensions. I deleted Cursor but still use the agent via Zed because it’s a lot nicer experience, Zed never had popups telling me Grok is half off. I also use OpenRouter and Zed.dev with it, that’s three providers out of dozens that it supports.
Exactly. The more competitive the space is, the more important it is that products purposefully support 3rd-party providers. Now that people are increasingly switching from Anthropic/OpenAI for inference reseellers and on-prem compute, transparency and portability will be the new values, not being slightly better than the next agent or model.
I use this every day — https://zed.dev/blog/terminal-threads
This feels very useful for training agents but almost completely useless to humans? Do I really want to go back to every change I made? Whatuse would that be?
This makes me uncomfortable.
Maybe I’m pessimistic, but I think this just gives micro-managers the data they need to micro-manage you. It invites people to scrutinize the process, instead of the results.
Not once have I wished to review a colleague’s conversation with an AI. I want to review finished work.
I look at this and I can only imagine layoffs being justified with “bad prompt quality”. An incident retrospective broadcasting your agent conversations to the entire company, with people speculating where you should have put the “make no mistakes”.
It’s a shame, really, because I like Zed as an editor, but I can’t bring myself to support them if this is the direction they’re choosing.
Not only this. I'm also shuddering at the thought of how much more noise this adds which can only be filtered through LLMs.
Don’t worry, Zed (or another company in their VC backers’ portfolios) will helpfully sell you inference to filter through that noise!
I guess this data is not intended to be used all the time. But occasionally you may find it useful in blame or bisect or similar things.
The sort of company that would do those things is going to be mandating you to use their enterprise AI plan anyway, which already lets them read all your conversations if they want to.
Letting them read my conversations is okay. Systematically reconstructing a timeline of every keystroke that went into a project, then immortalizing this timeline into a VCS, that’s the creepy part.
I suppose companies could do this anyway just by installing spyware in your work computer, but I would very much prefer if that spyware was not my editor of choice.
It's also delusional to think you can find that one edit that was really useful but you forgot to commit but then deleted in another giant commit.
As anyone who's ever tried to split a days worth of work apart with `git add -p` is well aware.
It may be feasible with a million agents, but they could remember what they typed three hours ago anyhow.
The way I’m seeing AI used by organizations is to produce process slop: tickets, summaries, docs, etc. rather than drive process change and optimization, or enable individuals to be more effective within the organization.
I don't know. I've been giving Zed a chance for almost half a year now and it just doesn't seem to be going the way I would want an editor to go.
Previous discussion: https://news.ycombinator.com/item?id=48492533 (June 11th, 225 comments)
Is it available now? Still seems to be a waitlist?
I had the great pleasure/misfortune of being forced to work with LaminDB, and I can tell you folks; data provenance isn't going away -- it will be used to train the very AI models snapping at our heels
I really don't want management critiquing when I swear at Claude, thanks.
You can simulate this by having a jj repo with file system watches.
i think a system that uses git and file system artifacts (txt/md/xml files whatever preference) is much better. eng teams need to define their artifacts, eg plan file, reqs etc whatever is needed and important to that team. the agent convo itself doesn’t add much value IMO and adds unnecessary bloat.
So is this basically Beads + Dolt? This isn’t to diminish it, it’d be great if this ends up being a less “vibe code-y” alternative to those.
If not, beads + dolt seems like it would be pretty great.
this looks like jetbrains "local changes" but globally synced. "for the agents" mights scare people who jump to think about micromanagers, but these people mostly hide or fake work. even micromanagers will eventually give you an agent to use so it won't matter what is in the change log, what matters is speed+quality. and since you can iterate from any branch you have inginite try and retry possibilities
I have fallen in love with Zed.
I start to sound like a Jujutsu fanboy but...
Jujutsu already does this. I had agent screwing up changeset over couple hour long session and it took one shell command to split on pieces with longer pause.
The only downside is that because of Jujutsu snapshots it can't be used inside sandbox (since all jj commands are mutating)
Jujutsu is great, but it does not do this. It has no knowledge of agent sessions.
This local history has saved my bacon on occasion. E.g. when I went too long without committing and something silly overwrote the file I was working on. Or because I did something silly with git. Then it is nice that there is still an independent backup elsewhere with different failure modes.
Like a branch on the server?
That would still be in git. The local history in IntelliJ works independently of any VCS.
Also I’ve had formatters botch files including changes I hadn’t committed yet. For that the local edit history is also useful.
I really do like Zed, it's snappier than VS code and with pretty good vim emulation. Even through SSH, the native UI allows for no network latency, compared to something like vim+terminal. Like many other posters, I do feel like the core editor is getting worse.
Some issues I've encountered recently at work:
- Routinely encounter bugs with the python language server, it's particularly slow when compared to using VSCode. All that snappiest disappears when finding symbols after the '.' is considerably slower than my typing speed.
- I found similar issues with C++ code bases.
- It's also so hard to debug when something goes wrong. I was trying to find out why pyright keep spinning on startup, but the "LSP logs" never show anything.
- Connecting via SSH always opens the repo in restricted mode, even though I check the "Trust all projects in" checkbox. Never happened before.
- Debugger UI is a mess. Make a run, stop the run, edit the task.json, try running again, and 2 tasks show up. One for the old and one for the new.
--
I stuck with it because I really do like the UI, the performance, and initially it seemed to be an improvement from VS Code for my workflows, but lately I've been moving back to code as it seems more stable. I don't really use agent features, so I don't think I'm the target customer for this or other priority Zed features.
I do see the usefulness of something like this, I'm interested to see if the new agentic style of programming will result in the "code" part of editors becoming second class (for the better) and will allow for more rapid development. Although I'm not looking forward to read my coworker's "threads" of how a feature was made, I have a feeling that it will be more difficult to read than the raw code, as from my experience, LLMs don't really employ terse and effective communication (might not be entirely fair, I found ChatGPT /study mode pretty good.)
--
Anyone know of a good replacement editor that might meet my usecase? I'm really a batteries included type of developer.
What problem does this product solve?
Collaborative (as in simultaneous multiplayer) editing I think, which has been Zed's mission since before LLMs were a thing...
See https://zed.dev/blog/introducing-deltadb but also https://zed.dev/blog/crdts from years ago.
Basically what IntelliJ calls local history. It is a feature that has saved my bacon. https://www.jetbrains.com/help/idea/local-history.html
Similar, but not as polished, also exists in VSCode and derivatives, named the same way. Definitely saved me a few times as well.
This saved me from accidental resets in the past. I learned it existed because the files were showing up in mdfind
Yes, I concur. Local History is wonderful; nice to see Zed getting its own version.
Ooooh, this is cool. I was unaware of this. Thanks for the link.
Is this closed source?
Snapshots have an intention behind them as a chunk that the programmer thought of. It has infinite flexibility depending on the programmer/team. IMO they are a necessary feature, but the article considers it a bug. It’s an explicit and deliberate chunking of code writing process which is what you want in a chaotic “collaborative” environment. The system doesn’t get to decide but you decide when to commit.
It should work with github inbetween commits, that i may use. Right now I'm using staging as an in bewteen in a dangerous way.
Rust cult stikes again.
I don't understand, what do you mean by this?
This is a big unsolved dev tooling problem. Glad someone competent is working on it.
Yes, but it saps away the time that could be used to improve zed.
Or it’s actively used to improve Zed faster (or more efficiently).
zed is open source, you are free to improve it on your own
Yes, it is open source, and I am not saying they should not do it. Chromium is also open source, but if they added too much nonsensical AI functionality, I would be upset. I am free to improve it on my own, but that does not mean I cannot express how I feel.
I have not gone to the Zed repository and created an issue telling them to stop developing DeltaDB because it takes away the maintainers’ time.