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.

> 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.

@eljojo @AndrewRadev "I don’t mind AI writing code for you"

you really should

@penny @dirtside maybe we can go straight to basics: I'll start by saying I don't believe in copyright. I know it's necessary in today's world, but I'm personally opposed to it. I think it's a true reflection of capitalism and this world is much more worse off because of it than without.

Regarding AI, I believe there's a distinction between the theoretical technology and the current companies that deploy popular models. As well as downstream effects caused by them.

@amymagdalena are you open to having an actual conversation about this? or you just want to vent?

as a long time programmer, I legitimately don't understand why out of the sudden everyone started caring about which tools you used to write code

@eljojo All of a sudden? It’s been 3 years of slopfest now after a few years of shitty copilot autocomplete prior. And no, this is not similar to old instances of code automation cause they didn’t do all the logic for you, at most they gave you a bunch of boilerplate to fill in. So why did no one care, cause the tool was a keyboard and a brain and some generator scripts made by people with keyboards and brains, not a suped up Markov chain made without care.

And the reason people aren’t open minded with this with you, because you’re a long term programmer talking about something that has been clearly shitty for years, you should simply know better.

@amymagdalena regardless of "when it began", the bigger point is: why care about the tools I use to write code? shouldn't the code itself be what matters?

saying that people aren't open-minded because I simply should know better is also a bit silly, everyone has a different starting point for everything in life, you can't blame me for not knowing what you do.

I clearly am trying to fight AI slop myself, I published code about it on github, it's not like i've been living under a rock.

@amymagdalena I claim to write the code because I publish it under my name. I made the git commit. I take responsibility over it. If I hadn't logged into my computer, the code wouldn't exist. What else is necessary for me to claim ownership over it?

I'm a long term programmer, but that doesn't mean I'm supposed to know or experienced with equal degree everything you know. It's not fair to be shitty just because you don't agree with my current opinion.

There's literal javascript in the repo.

@eljojo @amymagdalena But you *didn’t fucking write it*! If my employer hadn’t paid me to write some code it also wouldn’t exist—but that doesn’t mean they wrote it! I wrote it!

Do you also claim to have written y.tab.c when you generate a parser with yacc or bison? I hope not, because *you didn’t write it*, even if you wrote the .y file from which it was generated.

Hope this clears things up.

@felipe @eschaton at what point do you consider the app to be built by you? what % of its lines do you need to write yourself to consider yourself a builder of it? what if you wrote the entire spec on how it needs to work, with very precise detail, but didn't actually write the code for it?

do you think product managers are not builders of apps?

@eljojo @felipe Product managers are not builders of apps, no. The people who actually write the code and maintain the build system and the tests are the ones who built the app.

Why does this seem so hard to understand? If you didn’t build it, you didn’t build it.