NerdNextDoor Mar 8

FINAL EDIT: We've been making good progress with EVi! We've fully settled on version 9.1.0 with no AI code, we're on IRC @ #evi irc.oftc.net, we've gained a lots of popularity and we've been working on fixing tests and removing platforms that are deemed exotic with other cleanups. Thank you to everyone who has supported us this week!!!

hard-forked vim at release 9.1.0 (Jan 2024)

https://codeberg.org/NerdNextDoor/evi

maybe we can get a group of people behind this??

Fuck AI.

#VIm #FuckAI #Tech #Technology

evi

EVi, a hard-fork of Vim v9.1.0 (Jan 2024) before AI was used in the project.

Codeberg.org
Show threadNerdNextDoor Mar 8
I thought about calling my fork cvi (for "Community's Vi IMproved") and starting at version 10.0.0 and making release dates be months, not days.
Show threadNerdNextDoor Mar 8

Made an issue on how this should proceed.

https://codeberg.org/NerdNextDoor/vim/issues/1

How does this continue?

In light of the events taking place on the upstream VIm repo, I hard-forked from release 9.1's code. Here's the plan I have including some options. The plan involves eventually renaming to CVI (Community's Vi IMproved), using year and month for releases instead of year, month and day. We'll...

Codeberg.org
Show threadNerdNextDoor Mar 8

Made a pull request to small-hack/open-slopware to add #VIm to the list.

https://codeberg.org/small-hack/open-slopware/pulls/38/files

#Codeberg #FuckAI

open-slopware

Free/Open Source Software tainted by LLM developers/developed by genAI boosters, along with alternatives. Fork of the repo by @gen-ai-transparency after its deletion.

Codeberg.org
Show threadNerdNextDoor Mar 8
Updated my fork to 9.1.2073 before the release of it, specifically, the last commit before the AI commit.
Show threadNerdNextDoor Mar 8

The first commit by me to the EVi editor, a fork of VIm before the AI slop.

https://codeberg.org/NerdNextDoor/evi/commit/99d7fe946837131607e0b1cacbb3fb9a63cb4a18

Introducing, the beginning of development on EVi 10.0. (Intended to leave behind VIm 9.1/9.2.)

Beginning of EVi version 10 · 99d7fe9468

From today onwards, we distance ourselves from the upstream VIm by branching off from the last commit before AI was used. This will take a lot of work, but I believe in this project.

Codeberg.org
Show threadJoe WMar 9

@mrmasterkeyboard Just a (stupid) question: I think vim is pretty much there. Has been for a decade or so, I wrote lots of code and research papers using it.
Are there really important features missing?

That said (written): good catch, good initiative.

Show threadEntirio RotokolyMar 9

@drchaos

Sounds a little bit as if you wanted to say you can use the old codebase forever with no maintenance. I may have misunderstood/over-interpreted you, anyway some contradiction:

It definitely makes sense to maintain an old software even when it's under feature freeze.

Libraries which you depend on do change, compilers get new warnings, sometimes even operating systems do change. Most crucial for evi would be commonly used text terminals appearing/disappearing. Occasionally there could be a severe bug. Newer folks are used to different kinds of documentation, so it may make sense to adapt this.

In mid-term it could be considered what to do with xxd etc. which are by-packages of vim but seem to work rather independently.

@mrmasterkeyboard

Show threadJoe WMar 9

@hierkiosk @mrmasterkeyboard Overinterpreted maybe, and I hope I have not come across as dismissing of your effort.
Thanks for explanation!

Edit: and I was wondering about whether vim would need new features or "just" (yeah....) keeping it working.

Show threadEntirio Rotokoly

@drchaos

It's all fine. The effort I put into the vim/evi stuff is pretty small compared to the effort others make (side-eying @mrmasterkeyboard) and I don't feel it is dismissed anyway.

Mar 10 at 9:05amWeb