Forgot your password?
typodupeerror
Open Source

Vim Classic 8.3 Launched as an AI-Free Vim Fork (linuxiac.com) 57

This month saw the release of Vim Classic 8.3, the first stable version of a new long-term support fork of Vim maintained without generative AI tools. Linuxiac reports: The release is based on Vim 8.2.0148 and includes selected bug fixes and patches backported from later upstream Vim releases. Vim Classic was first announced by [SourceHut's CEO/founder] Drew DeVault in March 2026 after he objected to LLM-assisted development in Vim and Neovim. In his announcement, DeVault said he no longer wanted to use software developed with LLM assistance and introduced Vim Classic as a fork for users who want to continue using Vim without that involvement... Vim Classic follows Vim's charityware model and continues to direct users toward Bram Moolenaar's long-running support for children in Uganda. The release is distributed as a signed source tarball from SourceHut, while future important announcements are expected through the project's mailing list.
"Vim is important to me..." DeVault wrote in March. (DeVault even tattooed "hjkl" on his right arm.) "[A]lmost every word I have ever committed to posterity, through this blog, in my code, all of the docs I've written, emails I've sent, and more, almost all of it has passed through Vim."

But DeVault wrote that he also cares about AI's impact on air pollution, fresh water supplies, global supply chains, and the working conditions of miners in African companies: And at a moment when the climate demands immediate action to reduce our footprint on this planet, the AI boom is driving data centers to consume a full 1.5% of the world's total energy production in order to eliminate jobs and replace them with a robot that lies... All this to enrich the few, centralize power, reduce competition, and underwrite an enormous bubble that, once it bursts, will ruin the lives of millions of the world's poor and marginalized classes.

I don't think it's cute that someone vibe coded "battleship" in VimScript. I think it's more important that we stop collectively pretending that we don't understand how awful all of this is. I don't want to use software which has slop in it. I do what I can to avoid it, and sadly even Vim now comes under scrutiny in that effort as both Vim and NeoVim are relying on LLMs to develop the software... To keep my conscience clear, and continue to enjoy the relationship I have with this amazing piece of software, I have forked Vim...

Since forking from this base, I have backported a handful of patches, most of which address CVEs discovered after this release, but others which address minor bug fixes. I also penned a handful of original patches which bring the codebase from this time up to snuff for building it on newer toolchains...

I invite you to use Vim Classic, if you feel the same way as me, and to maintain it with me, contributing the patches you need to support your own use cases.

Vim Classic 8.3 Launched as an AI-Free Vim Fork

Comments Filter:
  • by rossdee ( 243626 ) on Saturday June 13, 2026 @04:05PM (#66190644)

    Is there a list of other text editors that don't have AI ?

    • I don't know about a list but Emacs just adopted a no-AI position.

      On a wider level, Open Slopware [codeberg.org] is the site to check if you're about to adopt an application and would like to ensure the modifications being made to it are by humans. Be aware the maintainers have been harassed multiple times by AI addicts so... keep tracking the discussions and be prepared in future to have to DDG "OpenSlopware" to find the latest version.

      • by dbialac ( 320955 )

        Emacs just adopted a no-AI position

        Emacs rejected having another feature??? FFS, it's the original bloatware. It took decades for Eclipse to come around and supplant it as far as code editors go. Maybe ^a^i was already taken for some other function. So now emacs has everything but the kitchen sink and AI.

      • emacs is an editor?
      • Emacs came with AI long before any other editor (Eliza).
        • OK guys, I think it's pretty obvious in context we're talking about generative AI here? Eliza (and Lisp) are not examples of that. AI had a very broad meaning once, from expert systems to neural nets, but right now it's pretty much exclusively being used to refer to generative AI.

          Secondly, even if we weren't, the Emacs position is about maintenance of its code base. It does not want "AI" code contributions, falling into the same category as the maintainers of Open Slopware's domain.

    • Emacs!

      Even AI can't figure out how to count the parentheses in lisp!

      • by dbialac ( 320955 )
        Truth be told, most languages use a lot of parentheses, but they put them in an intelligent and readable place, not before the name of the function, task or operator.
    • Nano.

  • by MpVpRb ( 1423381 ) on Saturday June 13, 2026 @04:06PM (#66190648)

    I have talents and handicaps
    When I took my first programming class, I learned faster and deeper than any of the other students.
    Evidently, I have a strong talent for code.
    I can't touch type. I tried to learn and failed. I also failed to learn to play the piano.
    If I was forced to use vi, I would have failed as a software engineer.
    But, with an IDE, I have done very well over a 40+ year career.

    • by pooh666 ( 624584 )
      You were from a different culture but you are too limited to understand that, so you blame the tool.
    • Learning vi is about on the level of learning Roman numerals. It's not difficult, but you're also not missing much.

      • Learning vi has some residual value if you're trying to do something in a shell like a container or constrained image and it's the only editor available. But it's only a last resort when there is nothing else, not even nano.
      • Learning vi is about on the level of learning Roman numerals. It's not difficult, but you're also not missing much.

        So, it's six?

    • by huiac ( 912723 )

      I also failed abysmally at touch-typing: I'd been using a keyboard for too long by the time I gave it a shot.
      I first used (n)vi(m) when working on telephony middleware as a support engineer/web developer, because UNIX and editor of choice in my workplace; after a few weeks my fingers "got it", and I (and my two-and-two-halves fingers) never looked back.
      When subsequently working in VBA (the only available platform in that environment), I so missed the speed and facility afforded by vim.

    • by caseih ( 160668 ) on Saturday June 13, 2026 @11:34PM (#66191112)

      When I was a young college student I watched a professor working on some code in his office one day and saw how fast he was able to manipulate the text, cutting pasting, duplicating, all without hardly moving his hands. Ad hoc macros with the "." command were so powerful. I was very impressed and learned vi and never regretted it. vi definitely doesn't require touch typing! In fact I think it was designed for non-touch typers.

      Now I have used vim for 30 years and am handicapped without it. I don't care if it's vim class, regular vim, neovim, or some IDE binding mode. I'm no vim expert and I really only use a small set of commands and keystrokes, but I appreciate the efficiency. The editor doesn't cause me to succeed or fail as a software engineer, but it does make my life more pleasant.

  • Handcrafted, artisanal software!
  • with Vim when Fresh exists?
  • Probably doesn't have anyone left who can appreciate this. Like Regular Expressions used to be, frustrating for many, copied by most, but powerful in the right hands. It is also nice to have someone thinking more about others vs how they can profit.
  • See subject

  • If a person does not know programming "vibe coding" will produce Garbage. AI is great for security audits, testing and bulk edits. Great for producing Proof of concept code. I will continue to use real vim and hope these extreme purist fail.
    • by dbialac ( 320955 )
      Personally, I use vim, but barely. I don't know most of the features. I know the features carried over from vi, the cut and paste logic and when I upgrade a version of Linux, how to look up how to get rid of all of the shit put into the system vim configuration afterwards. I had to use an older system with a pre-vim plain-old vi. The only thing I missed was the cut/paste (yank, etc.). Everything else worked as expected.
    • I was fairly opposed to AI coding based on experience, but I've found the recent models more useful. I don't really mind what tools anyone uses as long as humans genuinely review all the code. Neovim is approaching "done" as a project with some longstanding "would be nice," features. I'd love to see those actually get implemented and if AI helps give the developers more energy for it then that's ok for me.
    • by allo ( 1728082 )

      Most such purity-forks fail. How many distributions package the GIMP fork glimpse?

  • Ahm.. what are LLMs doing in VIM in the first place? EMACS I can understsand, that always was a kitchen sink, but it feels like a really strange thing to include in VIM itself.

    • by caseih ( 160668 )

      Not sure what you're speaking about. VIM classic differs from normal VIM in that they do not use LLMs to help develop the editor itself, nor do they accept contributions from those that do. Where as the original VIM editor maintainers now use AI and LLM for bug fixing, feature developing, etc.

      • by jythie ( 914043 )

        Ah, I thought they were referring to inclusion of some kind of LLM based tool right in the editor, kinda like how various full IDEs now have one built (or plugged) in.

  • Good for them. They created a version that they like. I read the release notes for the vim release. Battleship wasn't listed as being vibe coded. it was listed as being an example of how to use the newer Vim Script 9 features.
  • Sorry if I have that wrong, but wasn't he outed as being a CP lover? Lunduke did a series of videos on this, did that ever get resolved? Here's the video: https://www.youtube.com/watch?... [youtube.com] isn't that the same guy?

Don't get suckered in by the comments -- they can be terribly misleading. Debug only code. -- Dave Storer

Working...