Earlier quoted context omitted.
If you can understand that some behavior is toxic and should be banned, then you should understand the people behind "cancel culture." Alternatively, if you see "cancelling" "cancel culture" as not "cancel culture", then you can understand the paradox of tolerance, and why an idealistic fully tolerant approach is not possible either way.
Banning someone is not the same as canceling them though. Banishment is just enforcement of boundaries. It gets rid of a problematic person in a specific space where their behavior is not tolerated. It's about the community, not the banished. Once the troublemaker is gone, that's the end of it. Everyone goes back to their normal activities. Cancel culture consists of people going out of their way to get a person bann…
Rust-lang/rust is adopting an LLM policy
61–70 of 74 posts
Re: Rust-lang/rust is adopting an LLM policy
#62Earlier quoted context omitted.
I don't disagree with you. I too hate disclosing LLM usage. I hate giving free advertising to trillion dollar corporations. There's also the fact people will probably look down on me for it and assume I'm incompetent because I used an LLM, and I've actually ended up sitting on reviewed and tested patches to open source projects because of this. However, we should be polite and respect their house rules. They are bein…
> I hate giving free advertising to trillion dollar corporations. Are you required to tell you used Anthropic™ (or whichever your AI provider of the month is) to generate this code, and not only that *an LLM* was involved?
Re: Rust-lang/rust is adopting an LLM policy
#63I really dislike every kind of rule that says something along the lines "if it's LLM generated you must self-disclose otherwise it is against the rules". Because this quickly leads to witch hunting and easy persecution of IC's under the pretense "it looks generated by an LLM" or they just investigate you and put you on cooldown from being able to contribute while they check for signs of "LLM-generated code". It's no…
Re: Rust-lang/rust is adopting an LLM policy
#64Earlier quoted context omitted.
I don't disagree with you. I too hate disclosing LLM usage. I hate giving free advertising to trillion dollar corporations. There's also the fact people will probably look down on me for it and assume I'm incompetent because I used an LLM, and I've actually ended up sitting on reviewed and tested patches to open source projects because of this. However, we should be polite and respect their house rules. They are bein…
> There's also the fact people will probably look down on me for it and assume I'm incompetent because I used an LLM I've seen so many arguments (mainly from non-developers) claiming that anyone who uses an llm to generate code doesn't know how to program. They can't understand the difference between people using an LLM to blindly churn out code, and people developing with an LLM to generate the boring bits
Re: Rust-lang/rust is adopting an LLM policy
#65Earlier quoted context omitted.
that is not what the policy says. it says "authors must disclose", "reviewers don't need to play detective", and "if a reviewer is not sure whether a post is LLM-created they should handle it privately, consulting mods". and the recourse is "go to this zulip channel", because closing a PR isn't the same as geting banned.
For the morale of the person who created the PR, closing every PR you make is pretty similar to just being banned
Are there some potential contributors who might be discouraged because of this policy? Probably. Will maintainers have less time wasted by obvious low effort changes and engagement? Also probably. A user of AI is, in the experience of many maintainers, way more likely to be lazy than engaged.
Re: Rust-lang/rust is adopting an LLM policy
#66In a nutshell: It's fine to use LLMs to answer questions, analyze, distill, refine, check, suggest, review. But not to create.
This implies that "create" is the hard part that we should not offload to machines. But IME all of the other things are the hard part. So basically it's fine to get the LLM to think for you and give you the answers as long as you understand Rust syntax well enough to type it all out yourself? This also seems like it will produce worse code, because it's preventing the LLM from doing the easy/boring part that it's goo…
Re: Rust-lang/rust is adopting an LLM policy
#67I think LLM policies which ban usage are ultimately self-defeating. They neatly switch concerns about quality of contributions to concerns about "AI slop". These two things are not the same. But the biggest problem is that they ignore the (unevenly distributed) future. The future: SWEs will no longer write code by hand. The era of hand coding is over. We only saw that for sure in the last 6 - 9 months. But it's over.…
Re: Rust-lang/rust is adopting an LLM policy
#68Earlier quoted context omitted.
No codebase worth being deeply invested in is deeply understood by anyone, including the original authors. The eternal maintenance argument is tiresome. If there is a problem in need of fixing, you figure it out, you do not depend on some author being available, and LLMs are exceptionally helpful in this regard as well. Then, if the LLM has trouble figuring out, so will another human. It is a code smell.
There are all kinds of projects out there that have had significant impact on the world, which were written and maintained over the course of years by a single, highly capable developer. The way people talk about code nowadays, just because they have more powerful authoring tools, is frankly disgraceful. Imagine if modern construction techniques had become a reason to stop caring about the natural beauty of wood grai…
Now, if you have program that is highly complex, written by a single author who is not you, hinging on the ongoing goodwill and capability of that single author, that is a liability you do not want to have, operationally. Again, that is just how it is.
Re: Rust-lang/rust is adopting an LLM policy
#69Earlier quoted context omitted.
No codebase worth being deeply invested in is deeply understood by anyone, including the original authors. The eternal maintenance argument is tiresome. If there is a problem in need of fixing, you figure it out, you do not depend on some author being available, and LLMs are exceptionally helpful in this regard as well. Then, if the LLM has trouble figuring out, so will another human. It is a code smell.
Strongly disagree. The obvious counterexample is in the foss world is ffmpeg, which I would submit is deeply understood by Fabrice Bellard. As a sibling points out, there are also various worthwhile single author projects. Outside the world of foss there are for example multiple games that are highly respected that were all entirely or largely developed by a single developer. Rimworld, Songs of Syx, Dwarf Fortress, O…
Bellard hasn't worked on FFMpeg since 2003.
Re: Rust-lang/rust is adopting an LLM policy
#70Earlier quoted context omitted.
> There's also the fact people will probably look down on me for it and assume I'm incompetent because I used an LLM I've seen so many arguments (mainly from non-developers) claiming that anyone who uses an llm to generate code doesn't know how to program. They can't understand the difference between people using an LLM to blindly churn out code, and people developing with an LLM to generate the boring bits
The drama around LLM use in game decompiling and other related hacking is very funny. I've seen "well maybe you should learn C++ instead of being lazy and vibecoding" a nonneligible number of times.
Yet another thing I won't be able to publish I guess. Sigh.