Vim's lead maintainer has fully lost his goddamn mind
-
@KatS @barubary @AndrewRadev don't switch yet. GNU is still discussing whether to allow LLM vomitted code contributions. Them of all projects not rejecting it on ideological grounds and some emacs manitainers seemingly liking LLMs is not a good sign though.
I will be MAD if I have to abandon emacs because of this shit
@lhp @barubary @AndrewRadev This is the new "floor is lava", isn't it?
-
@AndrewRadev unfortunately it's happening to curl, too
@steko @AndrewRadev My impression was that they use "AI assisted" code analysers that are rather a different technology from the slop parrots being used here in vim. Daniel has a firm (and negative) opinion about slop for multiple reasons, IIRC.
-
@KatS @barubary @AndrewRadev don't switch yet. GNU is still discussing whether to allow LLM vomitted code contributions. Them of all projects not rejecting it on ideological grounds and some emacs manitainers seemingly liking LLMs is not a good sign though.
I will be MAD if I have to abandon emacs because of this shit
@lhp @KatS @barubary @AndrewRadev Didn't Hurd recently get some vommits?
-
@AndrewRadev ugh.
I've been using vim for like.. 15 years? I thought it was unlikely to get caught up in the fad-chasing that seems to affect so many other editors.
I do not want to have to switch, but now I feel like I might have to@ansuz @AndrewRadev Switch to what though? VSCode?
-
@KatS @barubary @AndrewRadev don't switch yet. GNU is still discussing whether to allow LLM vomitted code contributions. Them of all projects not rejecting it on ideological grounds and some emacs manitainers seemingly liking LLMs is not a good sign though.
I will be MAD if I have to abandon emacs because of this shit
@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.
-
@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
