Zed's creators argue that Electron was the fundamental problem with Atom, not the ambition behind it. By writing the editor entirely in Rust and rendering every pixel on the GPU via their custom GPUI framework, they achieve sub-frame keystroke latency (~8ms vs 50-100ms in VS Code) and sub-500ms startup times. The result is a single native binary with no runtime dependencies — no JVM, no Node.js, no Chromium process tree.
Zed was designed from day one around real-time collaborative editing using CRDTs at the buffer level, rather than adding collaboration as an afterthought. The team positions this as fundamentally different from VS Code's Live Share, which was bolted on after the fact and can lose sync. This architectural decision reflects a bet that multiplayer editing will become a baseline expectation for professional editors.
The 1.0 release coincides with open-sourcing the entire codebase under GPL v3, while the GPUI framework gets the more permissive Apache 2.0 license. This dual-licensing approach lets the community build on the rendering framework freely while keeping the editor itself copyleft — a signal that Zed wants broad adoption and community contribution without enabling proprietary forks of the editor itself.
By surfacing the Zed 1.0 announcement to the HN community (637 points, 221 comments), the submission highlights the significance of the team behind Zed: Nathan Sobo (Atom creator), Max Brunsfeld (Tree-sitter creator), and Antonio Scandurra. Their track record building the tools that shaped modern editor infrastructure lends weight to the claim that Zed represents a genuine architectural leap rather than just another editor project.
Zed Industries has shipped Zed 1.0, the culmination of a multi-year effort by the team that built Atom and Tree-sitter to create a code editor that is, in their words, "the editor we always wanted Atom to be." The release marks two inflection points at once: the editor is now production-ready by its creators' own standard, and the entire codebase is open-sourced under GPL v3, with the underlying GPUI framework available under Apache 2.0.
The team behind Zed has serious pedigree. Nathan Sobo created Atom at GitHub. Max Brunsfeld built Tree-sitter, the incremental parsing library that now powers syntax highlighting in Neovim, Helix, and Zed itself. Antonio Scandurra rounds out the founding team. After Microsoft effectively mothballed Atom in December 2022, this group set out to prove that Electron was the problem, not the ambition.
Zed is written entirely in Rust and renders every pixel — text, UI chrome, menus — on the GPU via GPUI, a custom framework that treats the editor like a game engine rather than a web page. The result is a single native binary with no runtime dependencies: no JVM, no Node.js, no Chromium process tree eating your RAM.
The performance story is the headline, and it's not subtle. Zed targets sub-frame keystroke latency — roughly 8 milliseconds from keypress to pixel update — compared to the 50-100ms typical of VS Code running on Electron. Startup lands under 500ms. Large files open near-instantly. Memory usage is a fraction of a comparable VS Code workspace. For developers who spend 8+ hours a day in an editor, these aren't vanity metrics; they're the difference between the tool disappearing and the tool getting in the way.
But raw speed isn't what makes Zed architecturally interesting. The editor was designed from day one around real-time collaborative editing, implemented with CRDTs (Conflict-free Replicated Data Types) at the buffer level. This isn't a Live Share bolt-on that sometimes loses sync; it's multiplayer in the data model. Shared terminals, shared diagnostics, and live cursors are first-class features, not afterthoughts.
The AI integration follows the same philosophy. Zed ships with a built-in assistant panel supporting Claude and GPT-4, where you can select code, ask questions, and get inline transformations without leaving the editor. Unlike VS Code, where AI features arrive via competing extensions with different UX patterns, Zed treats AI assistance as part of the core editing experience. Users bring their own API keys — Anthropic or OpenAI — keeping the data flow transparent.
The open-sourcing under GPL v3 sparked the predictable licensing debate. Some developers wanted MIT or Apache 2.0 for maximum permissiveness. But the GPL choice is strategic: it ensures that forks must also be open-source, protecting Zed Industries' ability to differentiate on hosted services while preventing a proprietary fork from eating their lunch — the exact fate Atom suffered when VS Code, backed by the same parent company, cannibalized it.
The honest assessment: Zed is the best-feeling editor most developers have used, and also not yet a full VS Code replacement for most workflows. The extension ecosystem is where the gap is widest — VS Code's marketplace has over 40,000 extensions covering every language, framework, debugger, and niche tool imaginable. Zed's extension system supports language grammars and themes but is still early. If your workflow depends on a specific VS Code extension — a particular debugger, a framework-specific tool, a remote development setup — check before you switch.
That said, several categories of developers can switch today with minimal friction: Rust developers (excellent out-of-box support via LSP), TypeScript/JavaScript developers with straightforward toolchains, Python developers using standard LSP setups, and anyone doing pair programming or collaborative code review. The multi-buffer editing feature — which lets you view and edit excerpts from multiple files in a single pane — is genuinely novel and changes how you navigate large codebases once you internalize it.
For teams evaluating Zed, the collaboration angle deserves particular attention. If your team already uses VS Code Live Share and finds it unreliable (a common complaint), Zed's built-in collaboration is architecturally superior. But it does route through Zed's relay servers, which may be a non-starter for organizations with strict data residency requirements.
Platform support at 1.0 covers macOS and Linux (the latter in preview). Windows support is absent at launch — a notable gap given that a significant chunk of professional developers work on Windows, either natively or through WSL. It's on the roadmap, but "on the roadmap" and "in your hands" are different things.
Zed's real competition isn't VS Code's current feature set — it's VS Code's ecosystem flywheel. Microsoft has the advantage of a decade of extension development, a massive user base generating feedback, and the resources to iterate indefinitely. Zed's bet is that performance, native collaboration, and integrated AI matter enough to pull developers across the switching cost. The open-sourcing is the accelerant: if the community builds the extensions, Zed can focus on the editing core and the hosted services that pay the bills. Whether that flywheel spins up fast enough is the billion-dollar question, but the Atom team has already proven they can build an editor that captures developer love. This time, they're building on a foundation — Rust, GPU rendering, CRDTs — that won't rot under them.
What an abysmal series of top comments. These guys created a phenomenal product using novel technology, which will only continue to improve. Great work to the Zed team.
Congrats!My daily driver is Zed developing on SSH remote servers on exe.dev.It's crazy to think of all the dev tools I've churned through over the last 18 months but these two feel sticky.Zed has everything I need in a unified pane. File editor, terminal, agents, SSH remotes. And it's
I really want to like Zed because they've clearly put so much work into it, but so far I've been sticking with Sublime. I have several large PHP projects that were started in the 2010-2020 era, and Zed will highlight and complain about all sorts of minor things that were standard PHP fare
Too bad they did not include better search UI into this release.When you search, Zed opens a new tab, which I hate. Sometimes I just want to have a quick glance at some code and close the search using escape.Telescope style search in vim, helix or JetBrains tools is so much better.https://
Top 10 dev stories every morning at 8am UTC. AI-curated. Retro terminal HTML email.
Congrats to the Zed team for building the best modern editor I have ever used. I subscribe to the monthly plan just to give you guys the funding you need, even if my funding is a tiny drop in the bucket. I always wanted a feature rich alternative to Sublime Text that can run anywhere and do basicall