I've never told anyone how to do their activism, I've criticized the consequences of said activism, which I still haven't got answered, and the lack of objective arguments for this specific instance of activism, which I still haven't heard, except for "AI bad lol".

I've been rolling with the definition of slop that's kinda universally agreed on, that is low quality, spammy AI generated content, and I'd ask again for an example of that in vim, but since your definition is "LLM used = slop", I don't need to do that here I guess. Also, you've missed the irony of telling me to not tell people what slop is, while telling me what slop is right after.

I don't understand how you can be so dense to call that an easy problem that's just boom done. It's not about compiling and aliasing it, you can do that on probably any commit of vim. It's about the maintenance and longevity of the fork, who's gonna support it, and will it have a proper level of maintenance that will make it productively usable in the long term? It's been forked to a "pre-AI" state of vim, how is it known that it's not having LLM generated (as in LLM assisted) content already, before the official guidelines have mentioned that? If all that makes evi stand out is a strict no-ai policy, how is this gonna be checked and enforced (e.g human developer uses LLM tooling on his local machine, without disclosing it)? Who are the developers behind it, greetings from xz and similar supply chain attacks? How are upstream changes and fixes handled, since you'll use it at some point with elevated privileges or to edit sensitive files? But yeah, fuck all of that, it compiles and you can just alias it, right, so we can talk about the severe problems in the open issues - will vim script be renamed too, and we need to rename vimrc to evirc asap, and boom done.

I've said it here at some point already, screeching "AI IS BAD REEEE" is not helping the case, it's discrediting the "movement" or "activism" as a whole. AI will not leave. When the bubble bursts, people will stop shoving it everywhere, but it will stay where it can be used properly. Software engineering is something where it CAN be used properly, since whatever you're building doesn't give a flying fuck about who's been writing the code. It's either good, or it's bad. Instead of worthless decisions on principle, do better. Coach and talk with people on how to do better, how to live in a world with AI responsibly and for good. Avoid, boycott and fork the ones deciding to not do that, based on objective reasons, and build it better. That's what activism is about, using your actions to lead to change for the better, or isn't it? And I don't see how a hard fork, with all the mentioned consequences and problems, for the simple reason of vim maintainers saying "disclose AI usage" is leading to anything better just for the reason of shoveling an antislop and no-ai tag into the codeberg repository.