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

Zed is our office

zed.dev

Post reply on HN
Print view View original

41–50 of 343 posts

Re: Zed is our office

#41

Post by fragmede »

snerbles wrote: post #26
jes5199 wrote: post #21

I could imagine that in ten years git will feel strangely slow and ceremonial. Why not just continuously work and continuously deploy live-edited software

Often projects need a history of stable checkpoints, and source control is one way to provide that.

Yes, but does it need all the ceremony surrounding it? If, every time I saved the file, the changes were analyzed and committed to git, and a useful commit message included, and commits squashed automatically and pushed and tested and tagged (using magic, let's say); if the system existed in the background, seamlessly, how would our interactions with source control and with other developers look?

Re: Zed is our office

#43

Post by vablings »

electroly wrote: post #11
drcongo wrote: post #8

Earlier quoted context omitted.

It's just pair programming when you're doing it on code so if you can bear pair programming you'll be fine. Personally, I hate it.

Pair programming usually has a single "driver" on the keyboard to keep things controllable. Here, everybody is driving: "dozens of cursors are concurrently editing the same file in real-time."

The concept of sharing and taking turns has been lost on the software engineer here....

Re: Zed is our office

#44

Post by JamesSwift »

xrd wrote: post #19

I love Zed. I, mostly, love the direction they are taking the editor in. But. There are now two times I see Zed going in the wrong direction. The AI integration was one. This feels like the wrong direction again. I never really liked the AI integration. It felt off to me. I do love coding with Claude and I think I know why. It presents the "information I need to know" in a way my puny brain can handle it. Colored dif…

Man, Im like the total opposite in terms of preferring the Zed UI vs claude code. I really try to avoid raw claude when possible. I very rarely pull it up to do concurrent sessions when I have Zed open already working on something else. Or if I need to do something quick while in the CLI in a random directory. Otherwise, I think just the "files modified" feature is worth using Zed as the primary interface.

Re: Zed is our office

#45

Post by antoniojtorres »

mariusor wrote: post #42

Is this the new Zawinski's Law? Instead of extending to read email, Zed extends to enable chat and voice-video. :)

I’ve been using “The Notioning” for the last few years to refer to the convergence of tools like slack adding notion like features, clickup adding notion and slack type features, and so on. There seems to be a stable set of features that retains teams in an org

Re: Zed is our office

#46

Post by nixpulvis »

Octoth0rpe wrote: post #12

I _really really_ want to try this feature, but only if I can selfhost the collaboration server. If there is any way to do this, it's not obvious. Given that as I understand it, lots of project details will pass through Zed's servers, I can't imagine any enterprises would knowingly allow this without some kind of SLA with Zed.

It could be easier, but it is supported AFAIK: https://github.com/zed-industries/zed/issues/8260#issuecomme...

Re: Zed is our office

#47

Post by jes5199 »

mattnewton wrote: post #27
jes5199 wrote: post #21

I could imagine that in ten years git will feel strangely slow and ceremonial. Why not just continuously work and continuously deploy live-edited software

I feel the opposite way, that git branching and merging will become a bigger part of the job as more code is written by agents in parallel and then accepted by other agents or humans.

for now yes absolutely. but I’m already hearing rumblings that some people are having luck letting multiple agents edit the same directory simultaneously instead of putting changes through PR merge hell. It just needs coordinations tools, see https://github.com/Dicklesworthstone/mcp_agent_mail as one (possibly insane) prototype

for example it’s not out of the question that we could end up with tooling that does truly continuous testing and integration, automatically finding known-good deployments among a continuously edited multiplayer codebase

we’d have to spend a lot more energy on specifications and acceptance testing, rather than review, but I think that’s inevitable - code review can’t keep up with how fast code gets written now

Re: Zed is our office

#48

Post by nixpulvis »

I would love to see collab servers take the same path as LSPs in being standarized and integrated across various editors and IDEs. I would love to work more closely with my VSCode peers, for example. Of course some features may be outside the standard and only supported with likewise editors, e.g. voice chat perhaps, but having shared cursors and a text chat would be a good start.

Re: Zed is our office

#49

Post by Aurornis »

conradev wrote: post #25

If you've been a developer long enough, you might recall the teletype package for Atom—both built by Zed's founders. I first experienced this in SubEthaEdit in 2013 or so, but it has been around since the early 2000s : Appropriately working together on a truly collaborative tool, Martin Ott, Martin Pittenauer, Dominik Wagner, and Ulrich Bauer of Technische Universitat Munchen won the Best Mac OS X Student Project for…

SubEthaEdit was a very inspiring software project for me. The fact that a small team could, in a few months, produce an amazing app that solved real problems and gained notoriety was amazing.

As time goes on it feels like much of the low hanging fruit opportunities in software is disappearing faster and faster. I'm also a fan of Zed and everything they're doing, but it's notable that shipping next-gen editor software takes a lot more developer effort now than it did in the 2000s.

Post reply on HN