Nathan Sobo details Zed's engineering methodology and testing architecture prior to incorporating non-deterministic LLMs.
Prediction Not checkable as stated
Sobo: Custom architecture gives Zed control to build an AI-native editor
“Like the fact that we even made the investments necessary to Have enough control to deliver excellent performance and collaboration will also give us the control I think it takes to build sort of the first editor that's truly engineered from the ground up for …”
Opinion
Sobo: AI editor moats are shrinking rapidly due to better tool-calling LLMs
“So there's a, there was a lot of like integration work to bridge that gap, but now the LLMs, because they've taken on this tool calling and are getting better at tool calling, the story is the integration story has definitely gotten a lot easier. I think it's …”
Opinion
Sobo: Zed's competitive moat forces competitors to build an editor from scratch
“I mean, to me, the moat Z's moat is like implementing really nice product experiences with technical excellence and their performance, like just delivering a really great user experience that in order to compete with, you would have to Essentially build your o…”
Opinion
Sobo: Great code editors require low-level native graphics APIs, not web tech
“So I can see other points in the trade-off space making sense for different apps, but for an editor, I don't, I think this is what it takes to build the editor I want to use, put it that way.”
Opinion
Sobo: The ecosystem needs open agent APIs, not more VS Code forks
“Something that would make me happy is that instead of one more fork of VS code, people just had a great API for surfacing a great agent experience into a tool that was welcoming to that. We don't need to be sharp elbowed about controlling all of that.”
Assertion Partly supported
Sobo: The Zed editor reliably delivers 120 frames per second
“Zed runs at a 120 frames a second, reliably delivering frames.”