Live data from Hacker News

Zed DeltaDB

zed.dev

171–180 of 328 posts

Re: Zed DeltaDB

#171
post #89
post #72

Earlier quoted context omitted.

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.

Thanks. There maybe middle ground too like a Claude plugin.

I think Zed doesn't need to build this though.

Re: Zed DeltaDB

#172
To all the people complaining about not getting upstream fixes.. why don't you just fork it and fix it for yourself? The cost and difficulty of that is on the floor.

Genuine question, and to be clear I don't think you're wrong to be frustrated with upstream Zed

Re: Zed DeltaDB

#173

To all the people complaining about not getting upstream fixes.. why don't you just fork it and fix it for yourself? The cost and difficulty of that is on the floor. Genuine question, and to be clear I don't think you're wrong to be frustrated with upstream Zed

Being a maintainer of a popular open source package sucks. You get hundreds of PRs and it takes a considerable amount time to only merge the good ones. LLMs have only exacerbated the problem.

So to your question, if you submit a perfect fix upstream and it doesn’t get merged. You either deal with immense friction for which your company won’t understand to get it merged. Or you silently diverge from source.

Re: Zed DeltaDB

#174
post #75

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…

> Don't crash my entire PC when there's a large (100+ MB) JSON file in the working directory I don't think you can put this on Zed. An unprivileged userspace application, even if coded poorly, shouldn't crash the machine.

Sometimes OOM Killer can stop it before it wrecks too much havoc, but often everything grinds to a complete halt and I have to just power cycle.

Re: Zed DeltaDB

#175

Earlier quoted context omitted.

> Don't crash my entire PC when there's a large (100+ MB) JSON file in the working directory I don't think you can put this on Zed. An unprivileged userspace application, even if coded poorly, shouldn't crash the machine.

> An unprivileged userspace application, even if coded poorly, shouldn't crash the machine. How would you prevent that? It can write until root disk is full, can take all your memory, saturate your CPU and a whole bunch of other stuff we (users) like to be able to do for the things that need them. Unless you're suggesting something like Qubes or similar UX?

Disk, memory, and CPU limits? The app should crash, not the kernel.

Re: Zed DeltaDB

#176
post #168

VSCode is great, but its lack of a sandbox for extensions makes it extremely vulnerable to supply chain attacks. Zed is one of the few major editors that isolates plugins, which is why I like it. However, it has far too many bugs. Regarding DeltaDB’s request to 'log conversations and changes together', I think the Linux kernel's development model — which combines mailing lists, patch exchanges and Git — provides a go…

The problem with combining mailing lists, patch exchanges, and Git is that you have to combine mailing lists, patch exchanges, and Git.

Most projects are not created under those conditions.

Re: Zed DeltaDB

#177
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…

Is it? Last time I checked, I had to maintain a custom fork because they didnt support device auth for remote env so you couldn’t really use your chatGPT sub.

Re: Zed DeltaDB

#178
post #127

I kind of do the conversation tracing thing already. Every change is attributed by Claude code session id (and timestamped obviously), then I have a jq based tool over cc session jsons that I save indefinitely. I've found it very important to be loud about what I actually wrote vs what the llm wrote. Personal use solo repo. I don't know id want people seeing my cc sessions lol.

For others considering this, note that Claude removes session history files from ~/.claude after 30 days

Re: Zed DeltaDB

#179
post #88

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 f…

I think this is an evolution of Zed’s “multiplayer” CRDT features from a few years back, but with some new agent affordances.

Re: Zed DeltaDB

#180
If every commit has full ai conversation baggage, and you feed that history back to an ai… aren’t you wildly inflating context with stuff that may or may not matter? How does this even work with thousands of “commits?”
Post reply on HN