Live data from Hacker News

Zed DeltaDB

zed.dev

31–40 of 326 posts

Re: Zed DeltaDB

#31

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…

Not only this. I'm also shuddering at the thought of how much more noise this adds which can only be filtered through LLMs.

Re: Zed DeltaDB

#32
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)

Re: Zed DeltaDB

#33

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…

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.

Re: Zed DeltaDB

#34

Earlier 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

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.

Re: Zed DeltaDB

#35
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

Re: Zed DeltaDB

#36

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?

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.

Re: Zed DeltaDB

#37
post #21

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?

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…

> 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.

Re: Zed DeltaDB

#38
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

Re: Zed DeltaDB

#39

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 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.

Re: Zed DeltaDB

#40

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…

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!
Post reply on HN