mikaylamaki
Joined 4 years ago
Karma
202
Submissions
34
Member since
Jun 8
Recent submissions
Comment · 11 months ago
Comment · 11 months ago
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 planning on revisiting it once we have a few more features settled :D
Comment · 11 months ago
Unfortunately, we no longer support self hosting. We're planning on reintroducing it once we've polished the single player experience a bit more :)
Comment · 11 months ago
People have been doing collaborative text editing since the 60s actually! See, The Mother Of All Demos[0], referenced in our first blog post[1] :D
I'd say CRDTs are also a big change. CRDTs make live collaboration much more robust for all parties involved, and they only started to reach maturity in the mid-late 2010s
Comment · 1 year ago
It’s quite the experience
Comment · 1 year ago
Actually, Anthropic built that integration themselves.
Comment · 1 year ago
Yeah! It's a good sign that this idea is in the air and the industry is moving towards it. Excited to get rid of all the magic wands everywhere :D
Comment · 1 year ago
FWIW, we plan to sell "enterprise" builds of Zed with SSO, centralized plugin repositories, business-hosted infra, etc. etc. The sorts of features developers don't care about but businesses do. To do that, we have to be able to re-license the codebase and apply these changes. We have a lot of other ideas for business sustainability but the core, offline code editing experience will always be freely available and open source though :)
Comment · 1 year ago
The code gen example given later sounds an awful lot like what AWS built with Kiro[1] and it's spec feature. This article is kinda like the theory behind the practice in that IDE. I wish the tools described existed instead of all these magic wands
Comment · 1 year ago
We do! Sorry we missed your feedback.
Comment · 1 year ago
Agreed. The predict edit feature needs to be actively enabled before it'll do anything. And once it's enabled, it won't send up your private keys or environment variables. If their filename matches a glob in this list, or a list you configure.
Comment · 1 year ago
> a private key or API key could get sent, right?
You can disable this feature on a per-file basis, here’s the relevant setting: https://github.com/zed-industries/zed/blob/39c9b1f170cd640cd...
Comment · 1 year ago
Sorry you had this experience with Zed. We've seen a few reports of issues with our python integration (https://github.com/zed-industries/zed/issues/23170, https://github.com/zed-industries/zed/issues/22426), and we'll be taking a look at these next week. Please do a file an issue for performance problems like this, it's a bug if Zed isn't fast for your use case :)
Comment · 1 year ago
At Zed, we use our native collaboration to make sure we get a lot of synchronous time together. We also use it to do design review as we're coding a feature, letting us skip code review all together!
Comment · 2 years ago
We'd appreciate the issue and discussion! We've been aware of contrast issues for some time, and I personally have been thinking about switching our color representation from HSL to OKLCH to give us more traction on these problems. But I've been working on Linux and am not a designer, so I haven't had the chance :D
Here's our overall pitch: https://zed.dev/blog/sequoia-backs-zed#introducing-deltadb-o...