Earlier quoted context omitted.
We’ve been growing and have had to scale authentication beyond what our original collab server could handle. Not many people are using collab yet, we’re prioritizing non-collaborative features (like our recent Windows release), and we’re planning on rebuilding all of this on top of DeltaDB. Fundamentally, it just fell through the cracks. Self hosting will be a vital feature for users and enterprises though, we’re pla…
Looks like development of DeltaDB has been discontinued. https://github.com/delta-db/deltadb?tab=readme-ov-file#-upda...
Zed is our office
251–260 of 343 posts
Re: Zed is our office
#252Earlier quoted context omitted.
With the AI stuff, it feels like they invested a bit prematurely. When the Agentic editing demo came out (6 months, 10 months ago? It’s a blur), it felt right. Accepting and reviewing edits, live tracking ..etc., felt like pair programming. The ACP addition felt like a natural evolution . With the continuous improvement in CLI tools and people’s experience with them, it feels like doing a live review or edit-by-edit…
I used to only use JetBrains for AI stuff, now I just open everything in Zed because of its Claude Code integration. Especially with the linters and other nice to haves. I am insanely close to cancelling JetBrains.
I still use Claude Code in cli, as a WebStorm user.
Re: Zed is our office
#253I don't work at zed anymore but I do find it funny that anyone would think that the collaboration features of zed are "tacked on"... We started building zed in zed using it's collaboration in early 2021. Collaboration has always been part of it's DNA. Nearly everything at zed is written in pairs over collab.
I joined a Zed hackathon at RustConf 2024 where I built the "Open in split" functionality from the file fuzzy picker. A member of the engineering team who was floating around helping folks had us exclusively work through the included collaboration features. It was a great tour of the editor, and did not feel tacked on.
Re: Zed is our office
#254Earlier quoted context omitted.
In the case of AI tools it is for security reasons, not just reproducible toolchains.
We need more selinux and sandbox-exec in daily dev lives. There's no reason to bring a whole new system along just to restrict some access.
But irrelevant in this case. I dev on macOS. I’m not aware of any other options.
Re: Zed is our office
#255Earlier quoted context omitted.
We need more selinux and sandbox-exec in daily dev lives. There's no reason to bring a whole new system along just to restrict some access.
Docker is just a shim on kernel isolation APIs. It’s not any different, but better packaged. But irrelevant in this case. I dev on macOS. I’m not aware of any other options.
> It’s not any different
It's very different. With docker on Mac you're running a VM which runs a wrapped up complete system that runs your app.
With selinux/sandbox-exec you run just your app and can skip the extra packaging needed for docker and mounts. (And get the extra performance)
Re: Zed is our office
#256Earlier quoted context omitted.
Docker is just a shim on kernel isolation APIs. It’s not any different, but better packaged. But irrelevant in this case. I dev on macOS. I’m not aware of any other options.
sandbox-exec. It's not great, but it's usable. https://igorstechnoclub.com/sandbox-exec/ > It’s not any different It's very different. With docker on Mac you're running a VM which runs a wrapped up complete system that runs your app. With selinux/sandbox-exec you run just your app and can skip the extra packaging needed for docker and mounts. (And get the extra performance)
Re: Zed is our office
#257Earlier quoted context omitted.
Your company has a user pool, you sign a BAA or start working with a partner company that has their user pool. Instead of creating slack accounts in both you can share external slack rooms that only people that are invited in/from their respective orgs can join without having to co-mingle employee user pools.
But why would external partners want to look at your code? I guess if you're also integrating with them? But generally you just give them repo access instead. For Slack, it's different as messaging is a core feature to collaborate between different people in different companies, but looking at code is a very specific use case.
Code wise I guess you can could be working with any agency or contractors and you could collab on PR reviews? No idea to be honest.
Re: Zed is our office
#258I generally like what Zed is trying to become. However, all of these features and blog posts are frustraing when they struggle to keep basic editor features stable. Edit a file outside of the editor? It's not going to show up in the project pane or the git diff. Need to work inside a container because it's 2025 and we don't need to clutter our local machine with 100s of dependencies and env managers... well now all t…
yup, my pet peeve is there is no way to disable line wrap. the setting that exist doesn't work and there's no way to actually disable it instead of just increasing the max characters (with set hard limit in the source code). have a big docs or log,data file where you don't care for the rest of the line ? well too bad better have a spare editor. this feel to me like it should should be a number #1 priority. "an editor…
Re: Zed is our office
#259I have more to input here but I forgot some of them, overall, I just want to get back to vscode which is much easier and battle tested. I think zed have a totally different perspectives on feature sets and stuff, that's good, so people could have another choice. Hope zed could do great and I will definitely come back one day.
PS: I don't think collab worth too much effort in an IDE, you have much better tooling out there and have better intergrations.