NerdNextDoor 
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.
🧵
We are not a startup, we have few contributors and even fewer maintainers. We are a group of volunteers trying to continue VIm without AI slop code. We barely know each other. This fork started 3 days ago, be realistic please.
We're also trying to take on a codebase that has been going for decades that only has fallen to the dark side now.
From lobste.rs to Lemmy to Hacker News, we’ve been getting shit left and right in comments for forking the project. This is not everyone however.
(https://lobste.rs/s/izprt4/evi_hard_fork_vim
https://news.ycombinator.com/item?id=47321085
https://lemmy.org/post/4418940)
This isn't a political move nor an ideological one. Not a fork out of spite. This is a fork out of preventing bad AI code that is also fucking our environment from seeping into programs we love.
We don't hate VIm, nor the lead maintainer, but we do not support their actions.
I AM BANKSY ☕ / 🗑🔥@mrmasterkeyboard I don't understand why anyone should complain. ANYONE can fork the code for ANY reason, so long as it's in line with whatever licence applies to the code.
I hadn't heard about the vim troubles. I knew there were rumblings of something, but I hadn't yet looked what was up.
Thanks for taking the initiative and for raising my awareness. Looking forward to replacing vim installs.
@mrmasterkeyboard The comments complaining about this and gram being "political statements"
Yeah, sort of like how the EFF, copyleft, etc are politically neutral.
@xinit Thanks for not being some of the people in the comment sections that I've observed.
We forked it because we didn't want something that contributed to the current problems we have now or buggy code.
I don't get why anyone tried to politicise, ideologicise or try and put our fork in a position of wrongness in bad faith.
We're allowed to fork a project if we're not happy with it or want to add to it. If we weren't then projects like LibreOffice, FreeBSD and PostgreSQL wouldn't exist.
Kevin Karhan 
@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.
- This is how #Innovation is born.
- See #NetBSD, #OpenBSD, #DragonflyBSD, #OpenZFS, #Illumos, #Waterfox, #TorBrowser, …
Nit to mention EVERYTHING IS "#POLITICAL" - including "apoliticalness"!
@mrmasterkeyboard @xinit no, but I can imagine these places to be full of assholes just talking shite.
When I forked vim I acted in the face of objections that this was a mere waste of time and that it would be of no practical use to anyone.
I've learned to ignore such neighsayers when confronting them was out if the question…
Still I'm not one to squander my investment [in time and resources] and I remain confident this will be worth far more than the initial appraisal [in shitpostings recieved]…
Half-Life 2: Episode Two G-man Scene [Heart-to-Heart] (1080p)
@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!