Lapce

Original Article ↗ Hacker News Discussion ↗

A new Rust-based code editor, Lapce, is drawing interest as a fast, native alternative to Electron-based tools like VS Code, but many users report it still feels pre‑alpha, with crashes, UI glitches, missing basics (like reliable word wrap and keybindings), and rough platform integration. Commenters compare it frequently to Zed, Neovim, and JetBrains IDEs, weighing trade-offs between speed, maturity, plugin ecosystems, remote development support, and AI integration. The project’s maintainers emphasize that it’s a spare‑time, community effort that recently undertook the additional challenge of building its own cross‑platform GUI toolkit, so expectations should be tempered while it slowly stabilizes.

Project status and maturity

  • Many users report Lapce feels “pre-alpha”: hangs, crashes, odd window behavior, missing UI pieces, and poor error messages across macOS, Windows, and Linux.
  • Some are surprised a project with ~30k GitHub stars is still this rough; others note it’s maintained by a tiny part‑time team and a full native GUI is a huge effort.
  • A core developer explains it started as a personal project, is still volunteer‑run, and recently switched to a custom GUI toolkit (Floem), which introduced new bugs but is seen as strategically important.

Performance, memory, and “speed”

  • Users like the idea of a fast, native, Rust-based editor; some confirm fast startup and low latency when it works.
  • Others see high memory usage vs VS Code on the same projects, and noticeable UI latency or stutter; sometimes blamed on language servers, sometimes on Lapce itself.
  • Broader debate on whether speed/latency really matter: some say VS Code is “fast enough”; others are very sensitive to small lags and consider responsiveness a major UX factor.

Features, plugins, and ecosystem

  • Lapce has LSP/DAP and remote SSH support (though some parts, like GUI file pickers, are incomplete).
  • Plugins are WASI‑based; they can be written in any language compiling to WASI, but most current plugins are in Rust.
  • Maintainers explicitly do not plan to support VS Code extensions because that would require bundling the VS Code/Node runtime.
  • Users want word wrap, better Vim emulation, line wrapping options, tooltips, keyboard layout support, and stable remote dev.

Comparison with other editors (Zed, VS Code, Neovim, JetBrains, etc.)

  • Zed: seen as more mature, with collaboration features and commercial backing, but currently macOS‑centric and with licensing concerns for some.
  • VS Code: praised for ecosystem and remote dev, criticized for RAM, latency, and Electron stack.
  • Neovim/Helix/Emacs: many say once they’ve invested in a terminal editor plus LSP/plugins, GUI editors are a hard sell unless they match vim‑like behavior and collaboration needs.
  • Some specifically seek a native, cross‑platform GUI alternative to VS Code with strong remote dev and AI integration; Lapce is not there yet.

Business and OSS stance

  • Lapce is not a business and reportedly doesn’t even accept donations.
  • Discussion contrasts it with “open core” or VC‑backed tools but notes Lapce is fully FOSS with no monetization layer today.