@mwl Very very fuck. I am sick to my stomach right now. Don't know what to do with this information.

In desperation I started writing an email to the Foundation, but will sleep on it; I don't want to burn too many bridges until I fully understand where this came from, if it is final, what it actually means, etc.

But for fucks sake...I started looking at making an #evi port to replace Vim everywhere - and I'm not even a bloody Vim user!

This also comes with a huge problem for #EVi too considering we have Python support still.

You can read up on what we're thinking of here:
https://codeberg.org/NerdNextDoor/evi/issues/63

To quote me:
"I was thinking of potentially restricting what Python versions can actually interface with EVi. A hard limit. If Python identifies itself as anything past 3.14, we block it outright with a message to not support AI slop."

@justine Not a hardcore user but this shitshow has caused me to look very closely at EVi. As soon as it shows up in #FreeBSD #Ports I'll be replacing Vim everywhere I can reach - including at work.

I wanted to create that port but since there is no #EVi release yet, and the Vim port is fairly complex, I'll probably leave that to someone who is a "hardcore" user...

@justine I must inform you that we weren't sure of adding Kuroko to #EVi. It won't be done and it was merely a suggestion, hence the question mark in the title.

However, we are focussing on the possibility of freezing vimscript. We cannot, by ourselves without more people, maintain or continue to modify vimscript outside of regular maintenance.

To the people in the replies too, please look at our issue instead of taking the title at face value. It's a title, not what will happen for sure.