Lapce — Lightning-Fast Code Editor Written in Rust

What it is

Lapce is an open-source code editor written in Rust that prioritizes performance above all else. It uses GPU-accelerated rendering via wgpu to achieve sub-millisecond frame times and startup speeds that Electron-based editors cannot match. Lapce brings Vim-style modal editing into a modern GUI with first-class LSP support.

The editor targets developers who want the speed of terminal editors like Neovim with the visual polish of VS Code. It includes syntax highlighting via Tree-sitter, an integrated terminal, remote development over SSH, and a plugin system powered by WASI.

How it saves time or tokens

Lapce eliminates the lag that slows down editing in large codebases. GPU rendering means scrolling, searching, and navigating remain smooth regardless of file size. The modal editing system reduces keystrokes for common operations, and the built-in remote development support lets you edit files on remote servers without configuring separate SSH tools.

The WASI-based plugin system runs extensions in a sandboxed WebAssembly runtime, so plugins cannot crash the editor or introduce security vulnerabilities -- a common pain point with VS Code extensions.

How to use

1. Install Lapce: brew install --cask lapce on macOS, flatpak install dev.lapce.lapce on Linux, or download from lapce.dev.
2. Open a project directory. Lapce auto-detects language servers for syntax intelligence.
3. Use Vim keybindings by default (h/j/k/l navigation, i for insert mode) or switch to a standard keybinding mode in settings.

Example

# Install on macOS
brew install --cask lapce

# Install on Linux via Flatpak
flatpak install dev.lapce.lapce

# Open a project
lapce ~/my-project

# Remote development via SSH
# Use the remote connection panel in Lapce to connect to a server
# Edit files directly on the remote machine with local UI performance

Related on TokRepo

• AI coding tools -- editors and IDE tools for AI-assisted development
• Automation tools -- developer productivity utilities

Common pitfalls

• Lapce is under active development and some features available in VS Code or Neovim may not yet have equivalents; check the plugin registry before switching full-time.
• GPU rendering requires a compatible graphics driver; on headless servers or minimal VMs, Lapce may not start without a display server.
• The WASI plugin ecosystem is smaller than VS Code's marketplace; evaluate whether your essential extensions are available before migrating.