zed-industries/zed

Zed is worth a look if you want an editor that feels native rather than Electron-based, but go in knowing that the bundled GUI framework is no longer a general-purpose project and that platform coverage stops at the three desktop OSes.

The problem

You open a large repository and want to move between files, search, edit and pair with a colleague without the editor becoming the slow part of the loop. Traditionally that means either a heavy IDE stack that carries a lot of configuration and extension baggage, or a lighter editor that needs plugins to cover collaboration and language work. Zed's answer is a single native editor that renders through the GPU and treats multiplayer editing as part of the product rather than an add-on. The visible change is that navigation and typing happen in the same window you already use for coding, with no browser runtime in the middle, and that a second person can join the same buffer directly. Download and package-manager paths are listed for macOS, Linux and Windows.

What's different

The mechanism is the interesting part: Zed is built on its own Rust GUI library, GPUI, which draws the interface on the GPU rather than composing native widgets. That is why the editor can feel immediate in a way browser-based editors often do not, and it is also why the project is tightly coupled to one rendering stack. The maintainers recently moved the graphics layer from blade to wgpu, a change that generated substantial discussion. A commenter who follows Rust GUI libraries framed the willingness to build GPUI for a real application as a confidence signal, since many Rust UI crates stay disconnected from shipped products (comment). The trade-off cuts both ways: because Zed's UI stack exists to serve Zed, the framework itself follows the editor's needs. A commenter quoted an announcement that GPUI development is being scaled back to work relevant to Zed's own use case, with a community continuation in a separate repository (comment, community continuation). If you are choosing Zed as an editor, this matters little; if you were hoping to adopt GPUI as your own UI toolkit, it matters a great deal.

Who should try it

Good fit: a developer on macOS, Linux or Windows who spends the day in a terminal and a text buffer, cares about input latency and file navigation, and wants collaboration built in without configuring a separate live-share plugin. A commenter described liking the speed, frequent updates and LLM integration, and said one missing plugin kept them on VS Code (comment). That is the realistic test: check whether the extensions you depend on exist. Poor fit: anyone who needs a browser-based editor, since web support is still tracked as an open discussion rather than an available build (tracking discussion), or someone who wants the editor's underlying GUI framework as a stable third-party dependency.

Requirements and limitations

Platform coverage is the first boundary. Zed ships for macOS, Linux and Windows only; there is no web build, so a Chromebook or browser-only workflow is out of scope for now. Installation is straightforward through direct downloads or each platform's package manager, and building from source has separate guides for macOS, Linux and Windows, which matters if you want to patch or contribute.

Ongoing upkeep is about the extension and language ecosystem, not the installer. The editor is under active development, so behavior and integration details can shift between releases. Licensing also deserves a look before you embed anything: the source is primarily GPL-3.0-or-later with Apache-2.0 components where marked, which is fine for personal use and ordinary contribution but relevant if you plan to redistribute a modified build. The README's license guidance is aimed at contributors passing CI rather than at people evaluating commercial reuse.

HotRepo's take

HotRepo has only one dated trending observation for this project: 92,332 stars on 2026-10-28, a day when it gained 65 stars. That is a single snapshot, not a trend line, so persistence of interest cannot be judged from it. The stronger signal is age and discussion volume: the repository was created in February 2021 and has drawn a 317-point Hacker News thread about its graphics-library switch (thread). Before committing, verify the extension coverage for the languages and tooling you use daily, since that is where the practical switching cost sits.