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

    • hperrin@lemmy.caEnglish
      81·
      3 days ago

      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.

    • balsoft@lemmy.ml
      2·
      2 days 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.