@pertho @justine right now #evi builds in exactly the same way as #vim does, so no porting necessary. Thankfully all that hard work got done years ago πŸ™‚
I've a couple of questions for hardcore #Vim users. Since the AI revelation will you be sticking with Vim ? If not are you watching #Evi and considering it ?

https://codeberg.org/NerdNextDoor/evi
evi

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

Codeberg.org
Configuring a new dev VM, and it came out of the build script with an *ancient* #vim. Now building #evi. I will then install #Copilot.vim in it because I am a pervert.

@mrmasterkeyboard @xinit if you refuse to acknowledge #ahitposters and their hate as legitimate but just respond calmly (if at all) you'll make their blood boil, heads implode and frustrate them the most.

  • Besides the "optics" of being a level-headed #maintainer who doesn't waste time trying to argue against those that already made up their minds is just professional.

I genuinely want evi to succeed, because this is an important stance to take:

  • If we allow the #Enshittification of fundamental tools in #tech we'll run the risk of being unable to maintain even the core functionality of ibfrastructure and systems.
    • Because the longterm ramifications of using #vommits of #AIslop / #SlopCode are not just unknown, but already happening incidents based around "#AI" / "#VibeCoding" show that this is at best extremely fragile…

In fact, I want simple and auditable systems - espechally in critical infrastructure - and it needs to be reproduceable and maintainable.

  • With human-written code one usually gets comments or can reason things out easily.
    • Worst-case even ask the original author "Why did you do that?" because an "AI" cannot take or face #Accountability or #Consequences per design!

#EVi

@mrmasterkeyboard @xinit the #RightToFork is elemental to #FLOSS and necessary for #OpenSource to exist.

  • As much as I'm not a fan of seemingly abandoned forks of my works, I am not in the position to restrict or ban those.
    • And people OFC have their right to make a #fork whenever they want to do so!

We ain't criticizing corporations that maintain outdated inhouse forks out of principle, and I think that #evi isn't a "fork for the sake of forking" but actually does things different and apparenty "irreconcileable" to the mainline Project.

Nit to mention EVERYTHING IS "#POLITICAL" - including "apoliticalness"!

Forks Β· greyhat-academy/lists.d

List of useful things. Contribute to greyhat-academy/lists.d development by creating an account on GitHub.

GitHub

A monument to the past: https://codeberg.org/Steinar/bram-vim

Where the hopeful future happens: https://codeberg.org/NerdNextDoor/evi

☺️

#evi

bram-vim

Vim v9.0.1676 – Bram Molenaar's last commit and tag for Vim.

Codeberg.org
very productive (and slightly stressful) day for #EVi today but still all good

Also, to add to this entire thread.

If it seems like we're doing nothing for hours on Codeberg, there's a high chance we're on IRC. You can find us @ #evi on irc.oftc.net!

I've been scouring the web for peoples opinion on #EVi and I'm seeing a lot of unfair assumptions and judgement for a project forked 3 days ago.

Don't mind if I vent for a second? Please read.

🧡

#Tech #Technology #Vi #VIm

ICYMI - EVi, a hard-fork of Vim v9.1.0 before AI was used in the project. - Codeberg.org

https://codeberg.org/NerdNextDoor/evi

#evi #vim #ai #opensource
evi

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

Codeberg.org