How One Developer’s 32‑Year Stewardship of Vim Sparked a Fork That Surpassed the Original

Vim has been bundled with virtually every Unix‑based system for over three decades, reaching billions of devices worldwide. Bram Moolenaar began the project after buying an Amiga in 1988, improving the Stevie clone and releasing version 1.14 in November 1991. He named it Vi IMproved (Vim) and kept the abbreviation constant.

Moolenaar, a Delft University of Technology graduate, embedded a charitable appeal in Vim’s startup screen, directing donations to an orphanage in Kibalé, Uganda, through the ICCF Holland foundation he founded in 1994. The editor’s free‑software model and his personal stewardship meant that all core decisions—accepting or rejecting patches—rested solely with him.

In February 2014, Brazilian developer Thiago de Arruda submitted a multithreading patch. Moolenaar rejected it, citing its size and invasive nature, which conflicted with his conservative change‑management style. De Arruda then forked Vim, creating Neovim with the explicit goal of a complete rewrite: preserving key bindings while replacing the Vimscript language with Lua, adding true asynchronous job control, embedding capabilities, an integrated terminal, and LSP‑based intelligence.

Neovim’s development was funded via a Bountysource campaign that raised over US$33 000 against a US$10 000 target. While Moolenaar continued to maintain Vim independently, he later incorporated similar features—async support and a faster Vim9 script language—after observing Neovim’s progress.

After Moolenaar’s death on 3 August 2023, his family transferred ownership of the Vim GitHub account to the community. Christian Brabandt became chief maintainer, releasing Vim 9.1 in January 2024 and Vim 9.2 in February 2026, adding Wayland support, XDG directory compliance, HiDPI defaults, enhanced completion, and improved diff mode. The project shifted from a single‑author model to a collaborative team.

In March 2026, the community debated whether AI‑generated code should be accepted. Two factions created forks that outright reject AI contributions, while the main Vim line adopted a middle ground: an “AI usage policy” requiring explicit disclosure and standard style‑check compliance for any AI‑generated patches.

Popularity metrics show Neovim’s GitHub stars (~100 k) more than double Vim’s (~40 k). The 2024 Stack Overflow Developer Survey ranked Neovim as the most loved development environment (83% love rating), with combined Vim/Neovim usage accounting for 38.3% of developers.

Overall, the story illustrates how a single‑person open‑source project can evolve into a vibrant ecosystem, balancing stability and speed, navigating governance transitions, and confronting emerging challenges such as AI‑assisted code.