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

81–90 of 326 posts

Re: Zed DeltaDB

#81

Post by NortySpock »

yza wrote: post #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

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)

Re: Zed DeltaDB

#82

Post by sbankowi »

alfalfasprout wrote: post #36
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?

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.

Re: Zed DeltaDB

#83

Post by adulion »

yza wrote: post #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

why develop this when it seems jetbrains had a local history feature which recorded every change for the past decade(s)

Re: Zed DeltaDB

#85

Post by infogulch »

manmal wrote: post #21
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 ca…

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

Re: Zed DeltaDB

#86

Post by nirvdrum »

JaggedJax wrote: post #74
honeycrispy wrote: post #69

Earlier quoted context omitted.

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.

Re: Zed DeltaDB

#87

Post by dlisboa »

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?

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.

Re: Zed DeltaDB

#88

Post by quacker »

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.

Re: Zed DeltaDB

#89

Post by ibejoeb »

hahahaa wrote: post #72
ibejoeb wrote: post #39

Earlier quoted context omitted.

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.

Re: Zed DeltaDB

#90

Post by the__alchemist »

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?

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