Vim's lead maintainer has fully lost his goddamn mind
-
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 that........................... that is deeply horrifying
-
@AndrewRadev@hachyderm.io I used to think how much nicer the internet in general and FOSS communities specifically would be if people were a bit warmer and nicer to each other. Acknowledging others' contributions and ideas, thanking each other for good points etc. instead of the popular attempts to outnerd each other on technicalities.
Should've been more careful about what I wish for I guess...@kunev @AndrewRadev "the monkey's paw curls"
I've had minimal non-consentual contact with llm-app responses, but those leading sentences of a stochastic parrot reply really really get to me (due to people copypasting slop at me with zero human interaction/filtering/etc)
-
@barubary :exasperated groan: This may finally push me into switching to emacs, and figuring out how to make it functional as a replacement.
@AndrewRadev@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
-
@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
