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

111–120 of 326 posts

Re: Zed DeltaDB

#111

Post by enraged_camel »

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

"Almost unusable"? Slight hyperbole don't you think? I initially tried the Flatpak version on Fedora 44 and had a few minor problems, but since switching to the terra repos version (terrapkg.com) I've had zero issues, Have you tried that? For me, its a massive improvement over IntelliJ for my daily workflow.

>> For me, its a massive improvement over IntelliJ for my daily workflow.

That's a bit of a low bar. Perhaps that's the disconnect?

Re: Zed DeltaDB

#112

Post by hollowturtle »

> Every change is linked to the agent conversation that produced it

A total nightmare and imo every dev should push back using this stuff. You'd otherwise have management brag about you not being a good communicator with the ai agent, the same management that have no idea how to steer these tools.

I really like Zed the editor, I'm not sure I like the path they getting into

Re: Zed DeltaDB

#113

Post by danhite »

thangalin wrote: post #103
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?

From 1996: https://www.eng.auburn.edu/~kchang/comp6710/readings/They%20... "There is the software. And then there are the databases beneath the software, two enormous databases, encyclopedic in their comprehensiveness. One is the history of the code itself -- with every line annotated, showing every time it was changed, why it was changed, when it was changed, what the purpose of the change was, what specifications d…

also from ^ article on Lockheed Martin Corp space shuttle software group ...

  Importantly, the group avoids blaming people for errors. 
  The process assumes blame - and it's the process that is 
  analyzed to discover why and how an error got through. 

  At the same time, accountability is a team concept: 
  no one person is ever solely responsible for writing or 
  inspecting code. "You don't get punished for making errors," 
  says Marjorie Seiter, a senior member of the technical staff. 
  "If I make a mistake, and others reviewed my work, then I'm
  not alone. I'm not being blamed for this."

Re: Zed DeltaDB

#114

Post by usef- »

mynti wrote: post #51

This feels very useful for training agents but almost completely useless to humans? Do I really want to go back to every change I made? Whatuse would that be?

Jetbrains has had a "local history" feature for many years that had this, and I only use it occasionally but it feels pretty essential now. I once accidentally wiped uncomimted work in the terminal, and brought up Local History to restore it in a click. Or more casually, I'm struggling with a CSS design: what did it look like at 3pm? It's an effortless escape or experimentation valve between commits.

(It's also why you never need to manually save a file in jetbrains. It just assumes you want to save, because you can always safely go back if needed. Editors with manual saving feel cumbersome now)

Re: Zed DeltaDB

#115

Post by giancarlostoro »

hollowturtle wrote: post #112

> Every change is linked to the agent conversation that produced it A total nightmare and imo every dev should push back using this stuff. You'd otherwise have management brag about you not being a good communicator with the ai agent, the same management that have no idea how to steer these tools. I really like Zed the editor, I'm not sure I like the path they getting into

These sort of paper trails are for developers not management though, does your manager open all your commits and start commenting on them? If so, maybe apply somewhere else.

Re: Zed DeltaDB

#117

Post by prinny_ »

I guess an interesting use case for this would be to pinpoint exactly which change was made by who in cases where multiple people / agents work on the same code at the same time. The Zed team is working on two features that are probably going to be built on top of DeltaDB: async collaboration and instant sharing. Instant sharing used to be talked about more in the past and it's still the feature I am most eager to see.

Re: Zed DeltaDB

#118

Post by gigatexal »

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?

One could argue using WSL is an anti-pattern: use a real OS. I kid, I kid.

Yeah I’m an avid user of the editor. I don’t care for their AI stuff I bring my own but I just want to see the editor become awesome. A more detailed object plugin ecosystem would be nice.

Re: Zed DeltaDB

#119

Post by sarreph »

A lot of the copy on this page feels like the kind of copy an AI would produce. But I’m assuming, surely, Zed writes their own copy so I don’t want to accuse them of doing that.

Marketing aside, this is the kind of thing (advancements in VCSes) that I’d usually be excited about, but which I’m less excited about coming from Zed because it makes me start to worry that they’re going to continue focussing less on the core editor experience.

I love Zed and I hope that it doesn’t start to go flakey.

Post reply on HN