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 retrospecti…
Zed DeltaDB
31–40 of 326 posts
Re: Zed DeltaDB
#32Jujutsu 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)
Re: Zed DeltaDB
#33This 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 retrospecti…
Re: Zed DeltaDB
#34Earlier quoted context omitted.
Yes, but it saps away the time that could be used to improve zed.
zed is open source, you are free to improve it on your own
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.
Re: Zed DeltaDB
#35Re: Zed DeltaDB
#36Zed 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?
Re: Zed DeltaDB
#37Zed 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?
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 ca…
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.
Re: Zed DeltaDB
#38Re: Zed DeltaDB
#39Zed 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?
Having said that, I love the idea of correlating the agent sessions to the changes. I'm glad someone is working on it.
Re: Zed DeltaDB
#40This 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 retrospecti…
Not only this. I'm also shuddering at the thought of how much more noise this adds which can only be filtered through LLMs.