Microsoft’s new vim alternative is written in Rust???

Microsoft has launched edit, a lightweight command-line text editor built from scratch in Rust, designed to feel like classic MS-DOS-era editing while solving a specific Windows gap: 64-bit Windows ships without a default CLI editor. The project is small enough to bundle across Windows editions, aims for strong Unicode and terminal (VT) output for smoother SSH integration, and takes a modeless approach to avoid the “how do I exit Vim?” learning cliff that trips up new users.

edit’s core pitch is pragmatic. Microsoft says it wanted a small binary so it could ship with Windows variants without triggering image-size bloat fights, while still providing decent Unicode support. It also chose a VT-output-centered design rather than console APIs, explicitly to integrate cleanly with SSH. Mouse support is included, and the editor is positioned as a better baseline than Notepad for terminal workflows—something users can click through, select, and edit without wrestling with modal controls.

The Rust angle is central to the buzz. edit is fully open source under the MIT license and hosted on GitHub, with multiple contributors. The transcript notes that the Windows terminal team is behind the effort, and speculates that the project may double as an internal Rust exploration—especially since Microsoft has historically used C++ and other languages in similar areas. That speculation is reinforced by the way the project’s design decisions map to Rust-specific engineering tradeoffs: the team built a custom terminal UI library because existing terminal UI frameworks didn’t map well to plain C or were too large for the bundling constraint. An arena allocator is used to make Rust tree-building less painful, and the codebase is described as relatively compact—around 16k lines of Rust—making it a feasible reference for learning.

edit also reflects a deliberate rejection of existing editors. Microsoft compares options including Nano, Kilo, Micro, and Yori, and calls out why they didn’t fit the Windows default-editor requirements—either because they were too large to bundle or lacked first-party Windows support. The project’s modeless design is another key differentiator: instead of modal editing, it aims to behave more like familiar text editors, reducing friction for new users.

In practice, the editor is presented as functional rather than gimmicky: it supports basic file operations, navigation, undo/redo, and word wrap, with syntax highlighting kept minimal for plain Markdown use in the demo. Although the transcript claims Windows is the primary target, it also notes that building or running it on other platforms is possible by compiling from source.

The overall takeaway is that edit isn’t meant to replace Vim or Neovim for power users. It’s a default CLI editor for Windows—small, fast to learn, and engineered to meet OS-level constraints—while simultaneously serving as a public, MIT-licensed Rust showcase that Microsoft can use to test ideas and share them with the broader ecosystem.