@kunev "There, I fixed it"
Andrew Radev
Posts
-
Vim's lead maintainer has fully lost his goddamn mind -
Vim's lead maintainer has fully lost his goddamn mind@normalmode Yeah, interface decisions like method names etc live forever. Vim's strongest feature is how backwards-compatible it is. That's why I can have a folding plugin from 2006 installed in my config and it works perfectly 20 years later.
Running slop bots to "discuss" the API is the opposite of thoughtful. It's not like the project hasn't made bad calls about naming or types, but they have all been made with intent, at least, and people have learned from past mistakes.
At this point, I no longer feel like I can recommend anybody to update their Vim to get some new feature, since it's just as likely to contain a bunch of security issues or subtle bugs. I have already slowed my posting under @VimLinks because of stuff like this, but I think I'm fully done for the moment.
-
Vim's lead maintainer has fully lost his goddamn mind@normalmode There have been signs that their brains are going, but I didn't realize it had gotten this bad. E.g. the 9.2 announcement was visibly AI slop, and Christian Brabandt happily posted a "Warp AI" ad on the Vim github repo months ago: https://github.com/vim/vim/discussions/18153
But this particular PR really takes the cake, and it's only going to get worse from here on out.
-
Vim's lead maintainer has fully lost his goddamn mind> 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.
-
Vim's lead maintainer has fully lost his goddamn mind@danielsiepmann You and me both
-
Vim's lead maintainer has fully lost his goddamn mindThis 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.
-
Vim's lead maintainer has fully lost his goddamn mindVim's lead maintainer has fully lost his goddamn mind
-
Yesterday, had an argument with an AI booster.@xgranade The way that I personally interpret cases like this is a sort of "just world" belief. If it was truly bad, surely it would not be allowed? If there was a real problem, there would be some kind of higher power that stops it.
This also aligns with conversations where I point out that this stuff is heavily subsidized and the person says "well, it's free/cheap now", with no further elaboration. The implication is: "I will use it because I can. If it was bad to use, it would not have been usable."
If you believe that the status quo is good and just, then you don't need to consider anything outside of your immediate gratification. The consequences (to society or to your own brain) are someone else's problem. Once the rockets go up...
-
Duckduckgo has a survey for pro/anti-AI and I cackled so hard at the (current) results@lexfeathers And of course, even if you choose "No", DDG tell you how they're totally respecting that by making all their AI chat nonsense optional.
This is why when I open a private window with duckduckgo.com, I see two separate buttons with "Duck.ai" and if I make a search, I see both that, and also something rainbow-colored called "Search Assist". That's what they mean by "optional", they mean "we're actively promoting it and putting development effort into integrating LLMs with everything"
-
Zig is moving from Github to Codeberg: https://ziglang.org/news/migrating-from-github-to-codeberg/Zig is moving from Github to Codeberg: https://ziglang.org/news/migrating-from-github-to-codeberg/
Apart from avoiding the inevitable deterioration coming from Github being owned by Microsoft, they're also hoping to get less slop:
> As a bonus, we look forward to fewer violations (exhibit A, B, C) of our strict no LLM / no AI policy, which I believe are at least in part due to GitHub aggressively pushing the “file an issue with Copilot” feature in everyone’s face.
Good on them.