Discussion
EVi
lemonwaterlime: It would be nice if specific offending portions of the codebase were highlighted. As of now, it’s hard to see why one should use this fork. Also, since the source is available, anyone can just compile a past version of vim.
wffurr: A cursory search didn't turn anything up in the vim repo or elsewhere. I can see why the authors of the fork wouldn't want to stir up drama, but I am really curious too.
GaryBluto: Why am I entirely unsurprised that this anti-LLM hard fork is hosted on Codeberg? At this rate, how likely is it that Codeberg is just going to become a wasteland of abandoned ideological forks (with the exception of one or two major projects) by next year?
bilekas: I'm not sure what the angle of where it's hosted is.. Are you suggesting the project would have more legitimacy if it was hosted on github ?
GaryBluto: From what I've read of Codeberg it's user base is a tad tetchy and has a tendency to make mountains out of molehills. It was more of a comment on Codeberg than the project itself.
pointlessone: This kind of news are about nothing. Tell me in a year, even in 3 months, how your fork has been doing. Clicking Fork on gh and writing a blog post is not a fork. A fork is a lot of work. Color me surprised if this will even keep up with the upstream just filtering out the AI commits.
askl: Given githubs stance on AI "coding" it would be hypocritical to host the project on github.
bilekas: So it's a fork based on principle ? I'm a slop hater as much as the next one but that really does seem petty.
f311a: I tried to find any recent issues related to AI in the Vim repo, but did not find any.Offending commit https://github.com/vim/vim/commit/fc00006777594f969ba8fcff67...Just Claude as a co-author.
askl: There's a bunch of commits that have "supported by AI claude." as well. Whatever that's supposed to mean.
zzzeek: the lesson here is dont put those comments into your commits. use the tools you want to write code and just use them. it's nobody else's business. if someone overuses AI (which is common) it's quite obvious anyway
fergie: > it's nobody else's businessHuman origin certification is coming. It might be hard to enforce, but you should probably respect the intent if a project tries to enforce it.
vandyswa: Same motivation, different generation. I carry my own fork of vim 5.7, from around 2000. It did what I needed, and did it well, and I could already see where it was going.SMH at what I see in it now!
fwip: [delayed]
qalmakka: Honest question: why would anyone use Vim and not NeoVim nowadays? I've switched what, 12 years ago? And I've never had to look back. Just curious, to be honest. Especially since neovim is full of new features, while the Vim9 scripting language kind of tanked
mmooss: One reason might be how off-putting the Neovim community is, hijacking Vim discussions to denigrate an all-time-great, beloved work of technology and its creator (who did decades of work for free, gave it to the world, and gave any money to actual orphans) all for Neovim users'/devs' own egos, promotion, and obsession. Almost all of Neovim was made by Moolenaar, from concept to execution, and I don't know that I've ever seen any gratitude.I've never seen Vim users do that. If I had to choose, I'd use Vim.
jmclnx: Very nice, will look into it myself. Now if only they can set the defaults back to what vim 6.x used I will be happy.The new defaults drive me crazy and I had to update ~/.vimrc to disable them.This is what I had to add, but once in great while a default will be reset which I have yet to figure out why that happens. :let no_man_maps=1 :let loaded_matchparen = 1 :set comments="" :set matchpairs="" :set mouse= :set nocin :set nohlsearch :set noincsearch :set nois :set paste :syntax off """ disable autocomments :au FileType * setl fo-=cro """ turn off brace match comment matching set noshowmatch """ stop autoindent set noautoindent :filetype indent off ""set columns=80 set noundofile set showmode ruler " turn off a new vim 8 default set scrolloff=0
