A new editor branch called Vim Classic recently released its first stable version 8.3.0. The development team emphasized that all the code of the project was not generated with the help of a large language model (LLM). Vim Classic 8.3.0 is developed based on the earlier Vim 8.2.0148 version, and the team deliberately eschewed the newer Vim9 Script engine to reduce long-term maintenance burden and keep the code base simple. However, this trade-off also means that some modern Vim plug-ins that rely on new features will not work properly in Vim Classic.

The project maintainers stated that their starting point was to "clean up this version of Vim, prepare a release version of it, and imagine what a Vim 8.3 would look like without the Vim9 Script". In their view, compared to the upstream Vim project, Vim Classic lacks sufficient resources and internal knowledge reserves, so it is necessary to control maintenance costs by simplifying the technology stack. The team also admitted in the description that one of the costs of this path choice is the gap in compatibility with some existing plug-in ecosystems.

Although it is a "back to classic" fork in concept, Vim Classic still retains the "charityware" model of the original Vim, promising to continue to support the charity that the late Vim author Bram Moolenaar insisted on during his lifetime - providing help to children in need in Uganda. In order to ensure the security of this release, the developers emphasized that they have conducted a focused review of the security patches of upstream Vim and selectively incorporated changes that fix security vulnerabilities. They also reminded early adopters that there may still be flaws lurking in the system that have not yet been exposed.

The birth of this branch is closely related to the current industry controversy surrounding generative AI. The Vim Classic project was initiated by Drew DeVault. In a blog post published on March 25, 2026, he publicly expressed his strong dislike for generative AI, believing that this type of technology concentrates wealth and power in reality, promotes propaganda machines and even extremist tendencies, while producing a large number of "slop" (low-quality content) at the code and text levels. Since both Vim and NeoVim have accepted code contributions based on LLM-assisted generation, DeVault said that he could no longer continue to use these editors with a "clear conscience", so he chose to fork and maintain a route that does not accept AI code.

In upstream projects, Vim introduced a formal LLM-related policy in December last year, allowing contributors to submit code generated or assisted by AI, but the requirements must be clearly marked and ensure that the code is stylistically consistent with the historical code base. In contrast, a considerable part of the Vim/NeoVim user community is actively embracing AI tools, introducing functions such as code completion and "intelligent assistants" locally or in the cloud through various plug-ins. For example, some plug-ins focus on offline-first local coding assistance, some support switching queries between multiple external LLM services, and some plug-ins are specifically designed to run completion models locally, and even collaborate with multiple agents to complete task planning.

Against this backdrop of differentiation, the emergence of Vim Classic provides developers who are strongly opposed to generative AI with an alternative with a clearer value stance. For this group of users, choosing Vim Classic is not only a choice of technical route, but also an expression of attitude surrounding software development ethics, knowledge production methods, and open source community governance models. However, since the project has made obvious trade-offs in terms of functionality and plug-in compatibility, whether it can attract enough maintainers and users in the future remains to be seen.

access:

https://sr.ht/~sircmpwn/vim-classic/

tar.gz

vim-classic-v8.3.0.tar.gz

.tar.gz.sig

vim-classic-v8.3.0.tar.gz.sig