@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

@reiddragon well, @mrmasterkeyboard did #fork #vim at the last pre - #vommit point of the #git...

  • It's known as evi, which I think is a good name...
    • Maybe someday we get like nevi (basically neovim on #evi basis)...

Cuz I wish for that to happen, not only because I want to see a better #neovim but also because we better become more #intolerant to the #intolerable #Enshittification!

#vim #neovim #AI

evi

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

Codeberg.org