Viewing profile — mikaylamaki

That is a different project :D Here's our overall pitch: https://zed.dev/blog/sequoia-backs-zed#introducing-deltadb-o...

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-collaborat…

Unfortunately, we no longer support self hosting. We're planning on reintroducing it once we've polished the single player experience a bit more :)

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 chan…

It’s quite the experience

Actually, Anthropic built that integration themselves.

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

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 b…

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. …

We do! Sorry we missed your feedback.

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…

> 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/39c9b1f1…

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…

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 r…

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 t…

We have a flatpak build! It's not on flathub yet though :) https://github.com/zed-industries/zed/blob/main/docs/src/dev...

We have a few words on this in our troubleshooting guide: https://zed.dev/docs/linux#troubleshooting Let us know if that doesn't fix it!

Check out our troubleshooting page, you might not be utilizing the GPU! https://zed.dev/docs/linux#troubleshooting If that doesn't work for you, please file an issue, and let us kn…

We call them 'multibuffers' :D https://zed.dev/features#multi-buffers

As a Zed developer, our killer feature is the parallel programming that our software enables. It's like pairing without the terrible parts.

After we finished prepping this linux launch, we've started work on making this situation better. Follow along here: https://github.com/zed-industries/zed/pull/14034

That does seem more usable for this use case. I'll keep it in mind, thank you!

Roughly yes, though I'd caveat it with the specific application of the GPU: simple, 2D, UI elements. We've already built an abstraction that allows us to fluently build up a design…

Simply put: historical artifact and we want to own the stack. Zed was first created when these abstractions where a lot younger, and a text editor needs certain features, like IME …

Right now: mixed. We provide both user defined themes and theme overrides that let people color-correct things as they need, we have a strong cultural focus on keyboard accessibili…