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

201–210 of 326 posts

Re: Zed DeltaDB

#201

Post by blain »

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?

Although I agree and I hit same roadblock I found that wsl is working well when you open the project with special "projects: open folder in WSL" command, see my comment here: https://github.com/zed-industries/zed/discussions/26857#disc...

Nevertheless it could have been working better.

Re: Zed DeltaDB

#202

Post by grey-area »

echelon wrote: post #107
dlisboa wrote: post #87

Earlier quoted context omitted.

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…

> Every change is linked to the agent conversation that produced it. From any line of code, find the conversation. From any message, jump to the code it touched. This is how Zed leapfrogs the field and becomes a centicorn. If you can train a model to operate at a higher level and with looser requirements, you've gotten rid of engineers in the loop and built a system for the automated synthesis of high quality softwar…

Well this will certainly be an interesting test of your unbounded faith in a singularity based on word generators.

When do you expect them to become a ‘centicorn’ based on this fabulous technology?

Re: Zed DeltaDB

#204

Post by Thanemate »

umvi wrote: 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…

My annoyance with Zed is the inability to disable the "collaboration/multiplayer" functionality, so much that I'd rather just use VS Code.

Re: Zed DeltaDB

#205

Post by spockz »

exe34 wrote: post #104
spockz wrote: post #47

Earlier quoted context omitted.

That would still be in git. The local history in IntelliJ works independently of any VCS. Also I’ve had formatters botch files including changes I hadn’t committed yet. For that the local edit history is also useful.

Or add it to git? What's wrong with git?

The whole point is that sometimes I or the build system performs an action that it cannot reverse. This happens in between commits as I’m not in the habit of committing after every few keystrokes.

Re: Zed DeltaDB

#206

Post by anon7000 »

pknopf wrote: post #9

A non-existent problem that nobody asked to solve...

I think that:

1. Commits are really just manual checkpoints while you’re working. Why not automatically checkpoint everything so you can actually go back to an older implementation without needing to remember to commit it?

2. Agentic workflows are so deeply single player. It’s very annoying, I want to collaborate with my team with agents, not review the output of one dev’s agent which they’ll just shove back into their existing agent.

Re: Zed DeltaDB

#207

Post by anon7000 »

throwatdem12311 wrote: post #116

Please just make a good editor and stop getting distracted by AI nonsense.

1. There is not much money in making a good editor.

2. There is money in AI products, and a huge demand for solid AI workflows from many developers. Lack of AI tooling is absolutely a dealbreaker for many developers, whether you like it or not.

3. The core primitive here is just as much about enabling live collaboration which has been on Zed’s roadmap for many years before agents took over the industry.

Re: Zed DeltaDB

#208

Post by andsoitis »

echelon wrote: post #107
dlisboa wrote: post #87

Earlier quoted context omitted.

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…

> Every change is linked to the agent conversation that produced it. From any line of code, find the conversation. From any message, jump to the code it touched. This is how Zed leapfrogs the field and becomes a centicorn. If you can train a model to operate at a higher level and with looser requirements, you've gotten rid of engineers in the loop and built a system for the automated synthesis of high quality softwar…

I’ll have what you’re having.

Re: Zed DeltaDB

#209

Post by pjmlp »

neya wrote: post #165
dlisboa wrote: post #87

Earlier quoted context omitted.

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…

> They'll re-invent/re-write things constantly Re-invent is fine, that's how we actually get the good stuff we use. Re-write (frequently) is usually a sign of bad power dynamics in the team, code rot and generally bad engineering management, in my experience. That's why most React shops end up in this vicious cycle of constant re-writes of a perfectly fine working system for this reason. Yeah, must be really nice get…

Ah, but with re-writes you get to post those blog posts for Reddit and HN front page to drive traffic to the company's site, isn't that great?

Re: Zed DeltaDB

#210

Post by hresvelgr »

Commercially speaking, going against Git is a fool's errand. As much as I'd like to see Git usurped, I can't imagine the people backing this would sign off on a competitor to Git unless it was some type of sidecar. No doubt it'll be tightly coupled to Zed as well which is concerning. Perhaps this is pessimistic but I don't have faith the team are going to deliver anything groundbreaking given their entire business is existing technology, but less shit. No one is going to move core infrastructure for less shit or slightly better, otherwise we'd be using Mercurial or Darcs.
Post reply on HN