Vim's lead maintainer has fully lost his goddamn mind
-
Vim's lead maintainer has fully lost his goddamn mind
@AndrewRadev just to see if I understand. Are you having an issue with using Claude code for working with code or with the fact that he addresses claude like a person?
-
-
@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 "There, I fixed it"
-
> Thank you for the detailed feedback! I've addressed all the issues:
> Thank you for the feedback! I agree that following the Vim 8+ naming convention makes sense.
> Thank you for the feedback on naming!
> Thanks for the suggestion! After thinking about this more, I believe repeat_set() / repeat_get() is the right choice:
> Thank you for the feedback. A brief clarification.This isn't even rewriting his own thoughts in whatever bland style the chatbot can muster, it's just dumping people's comments into the bot and copy-pasting whatever it shits out.
This is The Future that boosters want: An endless bikeshedding session where agreeable chatbots trade excessively polite thank-yous and screenfuls of bullet-pointed lists. A bunch of children, getting paid to play around with tamagotchis.
What a bleak fucking future to dream of.
@AndrewRadev everyuone I talked to when the dumbass AI boom started told me not to worry but I knew straight away vibe coding trash will make things crap. Seeing people I used to look up to when I was a young developer are now AI zombies. My current, thankfully non-dev, work is impacted a lot with certain vendors releasing updates that break a lot of basic functionality. What a f-ing mess :(
-
Vim's lead maintainer has fully lost his goddamn mind
@AndrewRadev@hachyderm.io have you seen Lutris too?
-
@kunev "There, I fixed it"
misschien iets voor jullie @Noortjevee
-
@AndrewRadev just to see if I understand. Are you having an issue with using Claude code for working with code or with the fact that he addresses claude like a person?
@nihilistic_capybara @AndrewRadev can't answer for the OP but for me the issue is that at least two people in that PR are clearly putting stuff into Claude and then pasting the output directly on the issue.
-
> Thank you for the detailed feedback! I've addressed all the issues:
> Thank you for the feedback! I agree that following the Vim 8+ naming convention makes sense.
> Thank you for the feedback on naming!
> Thanks for the suggestion! After thinking about this more, I believe repeat_set() / repeat_get() is the right choice:
> Thank you for the feedback. A brief clarification.This isn't even rewriting his own thoughts in whatever bland style the chatbot can muster, it's just dumping people's comments into the bot and copy-pasting whatever it shits out.
This is The Future that boosters want: An endless bikeshedding session where agreeable chatbots trade excessively polite thank-yous and screenfuls of bullet-pointed lists. A bunch of children, getting paid to play around with tamagotchis.
What a bleak fucking future to dream of.
@AndrewRadev Sounds like every corporate/business email Iāve ever received. I fucking hate that style of communicating. Maybe itās just me, but I never say thank you in an email unless I really mean it!
-
Vim's lead maintainer has fully lost his goddamn mind
@AndrewRadev This might be what it takes for me to switch to Neovim, assuming they're not going the same way.
-
@nihilistic_capybara @AndrewRadev no it's very possible that chrisbra's response is passive aggressive to prove a point and that's the sort of thing I would conceivably do in a similar situation to be honest. Haven't quite needed to go that far yet.
Been using vim for 20 years but never followed development at all and this was not a good way to start.
-
> Thank you for the detailed feedback! I've addressed all the issues:
> Thank you for the feedback! I agree that following the Vim 8+ naming convention makes sense.
> Thank you for the feedback on naming!
> Thanks for the suggestion! After thinking about this more, I believe repeat_set() / repeat_get() is the right choice:
> Thank you for the feedback. A brief clarification.This isn't even rewriting his own thoughts in whatever bland style the chatbot can muster, it's just dumping people's comments into the bot and copy-pasting whatever it shits out.
This is The Future that boosters want: An endless bikeshedding session where agreeable chatbots trade excessively polite thank-yous and screenfuls of bullet-pointed lists. A bunch of children, getting paid to play around with tamagotchis.
What a bleak fucking future to dream of.
@AndrewRadev Is Shougu a native English speaker?
Some tolerance should perhaps be given to those who are not.
-
Vim's lead maintainer has fully lost his goddamn mind
Never trust anyone who uses their toddler as their avatar. Ever.
-
Vim's lead maintainer has fully lost his goddamn mind
@AndrewRadev which means @neovim is tainted as well because it regularly pulls changes from Vim. I'm not sure if someone in the Neovim team uses LLMs as well, they probably do.
-
@kunev "There, I fixed it"
@AndrewRadev @kunev I vividly remember having to discuss an essay article from the NYT or Guardian about "Visions of the future" for my English final exams in 2011.
In it the author described scenes where users' soon to be ubiquitous AR glasses, might show them likable cartoon characters from their youth instead of homeless people on the street.
This feels like that
-
@AndrewRadev This might be what it takes for me to switch to Neovim, assuming they're not going the same way.
@KatS @AndrewRadev There are "Claude" commits in both vim and neovim, so I'm basically committed to never upgrading ever again.
-
@KatS @AndrewRadev There are "Claude" commits in both vim and neovim, so I'm basically committed to never upgrading ever again.
@barubary Oh, hell.
Good to know, though; thanks.
@AndrewRadev -
@barubary Oh, hell.
Good to know, though; thanks.
@AndrewRadev@barubary :exasperated groan: This may finally push me into switching to emacs, and figuring out how to make it functional as a replacement.
@AndrewRadev -
Vim's lead maintainer has fully lost his goddamn mind
@AndrewRadev unfortunately it's happening to curl, too
-
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)