mikaylamaki

6 ms·

1.
by mikaylamaki 11mo ago
That is a different project :D Here's our overall pitch: https://zed.dev/blog/sequoia-backs-zed#introducing-deltadb-o...
2.
by mikaylamaki 11mo 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 pl
3.
by mikaylamaki 11mo 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 :)
4.
by mikaylamaki 11mo 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
5.
by mikaylamaki 1y ago
It’s quite the experience
6.
by mikaylamaki 1y ago
Actually, Anthropic built that integration themselves.
7.
by mikaylamaki 1y 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
8.
by mikaylamaki 1y 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
9.
by mikaylamaki 1y 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
10.
by mikaylamaki 2y ago
We do! Sorry we missed your feedback.
11.
by mikaylamaki 2y 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 l
12.
by mikaylamaki 2y 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...
13.
by mikaylamaki 2y 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-industri
14.
by mikaylamaki 2y 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!
15.
by mikaylamaki 2y 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
16.
by mikaylamaki 2y ago
We have a flatpak build! It's not on flathub yet though :) https://github.com/zed-industries/zed/blob/main/docs/src/dev...
17.
by mikaylamaki 2y ago
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!
18.
by mikaylamaki 2y ago
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 know whether you're using Wayl
19.
by mikaylamaki 2y ago
We call them 'multibuffers' :D https://zed.dev/features#multi-buffers
20.
by mikaylamaki 2y ago
As a Zed developer, our killer feature is the parallel programming that our software enables. It's like pairing without the terrible parts.
21.
by mikaylamaki 2y ago
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
22.
by mikaylamaki 2y ago
That does seem more usable for this use case. I'll keep it in mind, thank you!
23.
by mikaylamaki 2y ago
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, and then burn it down into a collection of recta
24.
by mikaylamaki 2y ago
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 support, that weren't as common back then. Further, own
25.
by mikaylamaki 2y ago
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 accessibility for all UI elements, you can increase or decrease the fon
26.
by mikaylamaki 2y ago
Unfortunately, the renderer is only one step in supporting an alternative platform. Even if we could have used Vulkan on every platform, the windowing APIs are completely different and those do most of the things we like our code editors to
27.
by mikaylamaki 2y ago
Partially because Kvark, who has a long history in graphics programming, was enthusiastic about it, and has similar values of simplicity and effectiveness to our own. Mainly because our renderer is simple enough that we would have preferred
28.
by mikaylamaki 2y ago
We use them every day at Zed for pair programming, we're rather fond of the features :D
29.
by mikaylamaki 2y ago
Yep! That's how we did it, with the heavy lifting done by the delightfully named "Aperture Science Handheld Portal Device" crate: https://crates.io/crates/ashpd
30.
by mikaylamaki 3y ago
Yes! In fact, that's one of our planned revenue sources, once we've fleshed things out :D :D

More ›