383
Vim's lead maintainer has fully lost his goddamn mind (media.hachyderm.io)
submitted 7 months ago by to c/fuck_ai@lemmy.world
97 comments fedilink hide all child comments
 

Related:

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

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.

https://hachyderm.io/@AndrewRadev/116176001750596207

@AndrewRadev@hachyderm.io

Christian Brabandt's comment on a PR: "I did pipe this through claude and he is not too happy about this:"
you are viewing a single comment's thread
view the rest of the comments
[–] 38 points 7 months ago (13 children)

I like this approach, but how can it be enforced? Would you have to read every line and listen to a gut feeling?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 13 child comments
    •
  • [–] 94 points 7 months ago (5 children)

    Basically the best you can do is continue as normal, and if someone submits something that says it is or obviously is AI, point to this policy and reject it. Just having the policy should be a decent deterrent.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [+] -12 points 7 months ago (4 children)

    It's okay, we're just not going to tell you 👍

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 9 points 7 months ago* (2 children)

    People submitting malicious or deceptive code to open source repositories isn’t a new phenomenon. Just know that if you do it with any name in any way attached to your real name, and anyone finds out, you can kiss your reputation in the software dev community goodbye.

    Also, if you don’t admit that it’s AI generated, and it turns out to be copyrighted code, you’ll have a fun time in court trying to defend yourself for copyright infringement by admitting to fraud.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 7 months ago

    If you vibe-code it and use an LLM to respond to reviews, it is really easy to tell.

    If you know what you're doing and just using an LLM to speed up boilerplate writing, honestly who cares. It is technically copyright infringement but so many people are doing it that it's not likely to be a problem.

    I think this policy is overblown a bit. A better policy is "you need to understand, and be responsible for, what every part of your contribution does". Enough to tell lazy vibecoders to fuck off, and allows for some flexibility in your tooling.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 25 points 7 months ago*

    Same mindset as "You don't need a perfect lock to protect your house from thieves, you just need one better than what your neighbors have."

    If a vibecoder sees this they will not bother with obfuscation and simply move onto the next project.

  • permalink
  • fedilink
  • source
  • parent
  • [+] -80 points 7 months ago (5 children)
    [removed by mod]
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 30 points 7 months ago (3 children)

    Tell us how you really feel.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [+] -57 points 7 months ago (3 children)
    [removed by mod]
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] -3 points 7 months ago (1 child)

    Ok that's really funny and I do agree with you, but I think you might be coming at this a little... unhinged. The issue with this is that it is unenforceable and honestly somewhat pointless. If AI tools are not up to scratch, then that will always be reflected in the quality of the code. Bad code is bad code, it doesn't matter what made it. A lot of people seem to think AI is synonomous with bad code, and if that is the case, simply ban bad code.

    The issue they are going to run into is twofold:

    Firstly, what qualifies as "using AI"? Admittedly I haven't actually read their licensing, but I'm just going to take a guess and say that it bans all forms of AI used anywhere in production. Almost every compiler I use these days has auto predict. It's rarely useful, but if it does happen to guess the rest of the code I was already going to type, and I accept that, did I use AI to assist my coding? Back in the day before it was an llm the auto predict was actually decent, so not all of them use AI. How would you even know whether your is AI or not?

    The second issue is an issue of foresight. When the AI tools do become up to scratch, that will be reflected in the quality of their code. Suddenly AI generated code is faster, more efficient, and easier to understand all simultaneously. Anyone using this license is effectively admitting that theirs is the inferior option.

    It's always hilarious to me when people ask whether something is AI slop. I dunno man, has your ability to detect whether something is good been reduced to AI slop? If it's good, it's good. If it's not, it's not. Either you like it or you don't. Feels very similar to transphobes saying they can always tell. If that's true, and AI really is always going to worse, you should never have to ask whether something is AI slop, you should just be able to tell. Otherwise it's just slop, no ai necessary.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 6 points 7 months ago*

    Firstly, what qualifies as "using AI"? Admittedly I haven't actually read their licensing, but I'm just going to take a guess and say that it bans all forms of AI used anywhere in production. Almost every compiler I use these days has auto predict. It's rarely useful, but if it does happen to guess the rest of the code I was already going to type, and I accept that, did I use AI to assist my coding? Back in the day before it was an llm the auto predict was actually decent, so not all of them use AI. How would you even know whether your is AI or not?

    So two things. First, it’s a policy, not a license. Second, the definition of AI generated is very clear in the policy.

    I don’t know why you would criticize it without reading it, but the main problems with AI generated code are legal, not quality related, and they are also clearly laid out in the policy.

  • permalink
  • fedilink
  • source
  • parent
    • load more comments (-1 replies)
    • load more comments (-1 replies)