Vim's lead maintainer has fully lost his goddamn mind
-
@ansuz @AndrewRadev Switch to what though? VSCode?
@cuboci @AndrewRadev most definitely not. I honestly have no idea.
neovim also has commits from claude, so that's not it either.
Maybe somebody will fork from a pre-slop version? -
@cuboci @AndrewRadev most definitely not. I honestly have no idea.
neovim also has commits from claude, so that's not it either.
Maybe somebody will fork from a pre-slop version?@ansuz @AndrewRadev I can't learn a completely new editor.
Vim/Neovim is muscle memory. -
@ansuz @AndrewRadev I can't learn a completely new editor.
Vim/Neovim is muscle memory.@cuboci @AndrewRadev I'm not gonna say I won't learn something new if I have sufficient reason to do so, but it would be incredibly frustrating to have to do so for such a ridiculous reason.
By all accounts Bram Moolenaar seemed like a good person, and it's terrible to see his project being (mis)managed in this way. -
@cuboci @AndrewRadev I'm not gonna say I won't learn something new if I have sufficient reason to do so, but it would be incredibly frustrating to have to do so for such a ridiculous reason.
By all accounts Bram Moolenaar seemed like a good person, and it's terrible to see his project being (mis)managed in this way.@ansuz @AndrewRadev To be fair, reading the conversation it seems the maintainer (chrisbra) used Claude to find problems with the proposed changes. The AI slop came from the PR author.
-
@simon_brooke@mastodon.scot @AndrewRadev@hachyderm.io what does it have to do with anything?
-
@Starcross@mk.absturztau.be @AndrewRadev@hachyderm.io Wait, damn, really?
-
@ansuz @AndrewRadev Switch to what though? VSCode?
-
@lhp @barubary @AndrewRadev Well, if I'm going to have to maintain my own locally-compiled fork of an editor, I may as well go the whole hog.
@KatS @lhp @barubary @AndrewRadev
Well frack, where do I take my text editing needs now? Which vi/vim variant hasn't been infected with this slop?
Or do I just go back to vi? I'll miss syntax highlighting and multi-staged undo, but don't really use any other vim features.
-
@KatS @lhp @barubary @AndrewRadev
Well frack, where do I take my text editing needs now? Which vi/vim variant hasn't been infected with this slop?
Or do I just go back to vi? I'll miss syntax highlighting and multi-staged undo, but don't really use any other vim features.
@nuintari @lhp @barubary @AndrewRadev Current status: checked out the latest 9.1.x tag of Vim, and running
make config. I think that's the last version not seriously tainted, but I'm happy to stand corrected.There's a non-zero chance I'll do similar with emacs, but I'm taking it a stage at a time.
-
@root @cuboci @AndrewRadev sorry, didn't realize we were doing a "wrong answers only" thread
-
@nuintari @lhp @barubary @AndrewRadev Current status: checked out the latest 9.1.x tag of Vim, and running
make config. I think that's the last version not seriously tainted, but I'm happy to stand corrected.There's a non-zero chance I'll do similar with emacs, but I'm taking it a stage at a time.
@KatS @lhp @barubary @AndrewRadev
We need a standard name prefix for projects that are "no vibe coding allow" forks of projects that have gone down the dumbass hole.
huvim, vim for humans, by humans!
-
@ansuz @AndrewRadev To be fair, reading the conversation it seems the maintainer (chrisbra) used Claude to find problems with the proposed changes. The AI slop came from the PR author.
@cuboci @AndrewRadev somehow I do not find it comforting that the last line against slop in software I use is review by another slop-machine
-
Vim's lead maintainer has fully lost his goddamn mind
@AndrewRadev @chainq feels familiar a bit
-
@cuboci @AndrewRadev somehow I do not find it comforting that the last line against slop in software I use is review by another slop-machine
@ansuz @AndrewRadev No, of course it's not. But the characterization of the maintainer as having "fully lost his goddamn mind" because he used an LLM to point out problems in a PR is a bit unfair in my view.
I wish he hadn't done it and anthropomorphising the slop machine and ascribing feelings ("not happy") to it certainly doesn't inspire confidence.
But open source projects are inundated with AI slop these days (just ask @bagder), that's why I only half blame him for trying to get on top of it. At least, that's my interpretation after reading the PR conversation.
-
@ansuz @AndrewRadev Switch to what though? VSCode?
@cuboci @ansuz @AndrewRadev i don't see any obvious code vomit on kakoune, but there isn't either a clear "no slop here", so it's kind of unclear how it will be in the future
as an option, not perfect, but there is kate, kde's code editor. if i weren't using kakoune already, kate would probably be what i'd be using instead, and it already is my backup in case i need
there is also vis, which seems mostly fine as well right now, but i haven't looked to deep into it
-
@ansuz @AndrewRadev No, of course it's not. But the characterization of the maintainer as having "fully lost his goddamn mind" because he used an LLM to point out problems in a PR is a bit unfair in my view.
I wish he hadn't done it and anthropomorphising the slop machine and ascribing feelings ("not happy") to it certainly doesn't inspire confidence.
But open source projects are inundated with AI slop these days (just ask @bagder), that's why I only half blame him for trying to get on top of it. At least, that's my interpretation after reading the PR conversation.
@ansuz @AndrewRadev Oh, and having followed the aftermath of Bram Molenaar's sudden death a little I think the current maintainer certainly had his work cut out for him and so far did it surprisingly well. I almost expected Vim to die a slow death. Bram didn't seem to have made many preparations for his succession. So I tend to cut the current maintainer a certain kind of slack.
-
@cuboci @ansuz @AndrewRadev i don't see any obvious code vomit on kakoune, but there isn't either a clear "no slop here", so it's kind of unclear how it will be in the future
as an option, not perfect, but there is kate, kde's code editor. if i weren't using kakoune already, kate would probably be what i'd be using instead, and it already is my backup in case i need
there is also vis, which seems mostly fine as well right now, but i haven't looked to deep into it
@SRAZKVT @ansuz @AndrewRadev Thanks for the pointer to Kakoune. Kate is out of the question though, not terminal-based.
-
This is in a PR where Shougo, another long-time contributor, communicates entirely in walls of unparseable AI slop text: https://github.com/vim/vim/pull/19413
What a pathetic state after decades of active, thoughtful work. "I asked the chatbot how to write this code", "Well, I asked my chatbot, and "he" doesn't like it". What a fucking embarrassment.
@AndrewRadev these people are old, exhausted, and dont want to code anymore.
-
@ansuz @AndrewRadev Oh, and having followed the aftermath of Bram Molenaar's sudden death a little I think the current maintainer certainly had his work cut out for him and so far did it surprisingly well. I almost expected Vim to die a slow death. Bram didn't seem to have made many preparations for his succession. So I tend to cut the current maintainer a certain kind of slack.
@cuboci @AndrewRadev I wish I had the patience left to be so charitable, but every project I've seen which has used LLMs in this fashion has eventually accepted PRs with glaring security holes.
Even if they're doing their best under difficult circumstances, it's still an unacceptable risk in my perspective, and I'm going to have to start seriously considering alternatives even if I don't switch immediately.
So, perhaps that slow death has already begun
-
@simon_brooke @AndrewRadev absolutely not a valid excuse. There are translation services that do not make you sound like an artificial twat.
Google Translate is fine for just about most things. I would much rather read “obvious Google Translate” slop because you can work backwards from ooorly translated text to find the original meaning.
AI slop strips out the original intent and replaces it with… slop.
