▲ 46 ▼ Rust May Limit AI-Generated Work in Its Core Repository (linuxiac.com) submitted 5 months ago by cm0002@lemy.lol to c/rust@programming.dev 7 comments fedilink hide all child comments
[+] abc@suppo.fi -23 points 5 months ago (5 children) Blanket AI bans are becoming the new slop. permalink fedilink source hideshow 5 child comments replies: [–] lavember@programming.dev 5 points 5 months ago (1 child) is this a blanket ai ban though? permalink fedilink source parent hideshow 1 child comment replies: [–] TehPers@beehaw.org 3 points 5 months ago* From the policy in the PR: The policy's guidelines are roughly as follows: It's fine to use LLMs to answer questions, analyze, distill, refine, check, suggest, review. But not to create. LLMs work best when used as a tool to write better, not faster. We carve out a space for "experimentation" to inform future revisions to this policy. So... No, it isn't. Note that there are times when using a LLM to create code is allowed. Reading the doc explains the nuance. permalink fedilink source parent [–] cm0002@lemy.lol [S] 6 points 5 months ago (2 children) Agreed, but hopefully they're being used more for "Let's pause for now while we figure out a good way to filter out true AI-Code-Kiddies slop from actual programmers using it as a proper tool" rather than perm bans permalink fedilink source parent hideshow 2 child comments replies: [–] TehPers@beehaw.org 4 points 5 months ago Actual programmers using it as a proper tool should produce output indistinguishable from actual programmers not using it at all. That there even is (often) a visible distinction is a big part of the problem. Notably, it even explicitly says in the proposal that it shouldn't require any policing. Instead, obvious cases are more important. permalink fedilink source parent [–] abc@suppo.fi -1 points 5 months ago Yeah, that totally makes sense. permalink fedilink source parent
[–] lavember@programming.dev 5 points 5 months ago (1 child) is this a blanket ai ban though? permalink fedilink source parent hideshow 1 child comment replies: [–] TehPers@beehaw.org 3 points 5 months ago* From the policy in the PR: The policy's guidelines are roughly as follows: It's fine to use LLMs to answer questions, analyze, distill, refine, check, suggest, review. But not to create. LLMs work best when used as a tool to write better, not faster. We carve out a space for "experimentation" to inform future revisions to this policy. So... No, it isn't. Note that there are times when using a LLM to create code is allowed. Reading the doc explains the nuance. permalink fedilink source parent
[–] TehPers@beehaw.org 3 points 5 months ago* From the policy in the PR: The policy's guidelines are roughly as follows: It's fine to use LLMs to answer questions, analyze, distill, refine, check, suggest, review. But not to create. LLMs work best when used as a tool to write better, not faster. We carve out a space for "experimentation" to inform future revisions to this policy. So... No, it isn't. Note that there are times when using a LLM to create code is allowed. Reading the doc explains the nuance. permalink fedilink source parent
[–] cm0002@lemy.lol [S] 6 points 5 months ago (2 children) Agreed, but hopefully they're being used more for "Let's pause for now while we figure out a good way to filter out true AI-Code-Kiddies slop from actual programmers using it as a proper tool" rather than perm bans permalink fedilink source parent hideshow 2 child comments replies: [–] TehPers@beehaw.org 4 points 5 months ago Actual programmers using it as a proper tool should produce output indistinguishable from actual programmers not using it at all. That there even is (often) a visible distinction is a big part of the problem. Notably, it even explicitly says in the proposal that it shouldn't require any policing. Instead, obvious cases are more important. permalink fedilink source parent [–] abc@suppo.fi -1 points 5 months ago Yeah, that totally makes sense. permalink fedilink source parent
[–] TehPers@beehaw.org 4 points 5 months ago Actual programmers using it as a proper tool should produce output indistinguishable from actual programmers not using it at all. That there even is (often) a visible distinction is a big part of the problem. Notably, it even explicitly says in the proposal that it shouldn't require any policing. Instead, obvious cases are more important. permalink fedilink source parent
[–] abc@suppo.fi -1 points 5 months ago Yeah, that totally makes sense. permalink fedilink source parent