// the take
Lapce is a native code editor written in Rust with its own GUI toolkit (Floem) instead of Electron or a text-based TUI. It targets developers who want VSCode-like features (LSP, remote dev, modal editing) without the memory/startup overhead of Electron apps.
Built-in LSP and remote development support are implemented from scratch rather than bolted on, and the proxy architecture (lapce-proxy) cleanly separates local UI from remote execution. WASI-based plugin system means plugins aren't locked to a single language like most editors require JS. Modal editing is a first-class citizen rather than an emulation layer, and the rope-based text engine (lapce-core) is a serious data structure choice for large file performance.
Floem is an in-house, still-maturing GUI framework, so UI bugs and missing widgets are more likely than with a mature toolkit like GTK or Qt bindings — you're depending on the maintainers' bandwidth for both the editor and its UI layer. Plugin ecosystem is tiny compared to VSCode's extension marketplace, so language/tool coverage beyond the built-ins is inconsistent. No mention of a stable plugin API or semver guarantees, which matters if you want to build and maintain a plugin long-term. Large single-repo Rust codebase with many interdependent crates (lapce-app, lapce-core, lapce-proxy) means contributing requires understanding the whole architecture, not just one module.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →