Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Zed DeltaDB

zed.dev

Post reply on HN
Print view View original

21–30 of 326 posts

Re: Zed DeltaDB

#21

Post by manmal »

NoDodgeQuestion wrote: post #6

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 can still make PRs. But, crucially, you can loop people in early on, when it matters the most.

Re: Zed DeltaDB

#23

Post by drdexebtjl »

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.

Re: Zed DeltaDB

#25

Post by spockz »

[deleted] wrote: post #22

[deleted]

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.

Re: Zed DeltaDB

#26

Post by a2800276 »

drdexebtjl wrote: post #23

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…

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.

Re: Zed DeltaDB

#27

Post by [deleted] »

drdexebtjl wrote: post #23

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…

[deleted]

Re: Zed DeltaDB

#28

Post by vulkoingim »

esafak wrote: post #8

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.

Re: Zed DeltaDB

#29

Post by 4lx87 »

drdexebtjl wrote: post #23

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…

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.

Re: Zed DeltaDB

#30

Post by exe34 »

spockz wrote: post #25
[deleted] wrote: post #22

[deleted]

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