this post was submitted on 16 Apr 2026
175 points (100.0% liked)
Programming
26563 readers
382 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
makes sense as a policy stance even if enforcement is basically impossible. the signal it sends matters more than the enforcement mechanism.
similar to how some projects have DCO or CLA requirements โ it's not foolproof but it sets a cultural standard for contributions. projects that care about their codebase provenance can at least point to a policy.
the quality argument is the more practical one imo. if LLM code in contributions correlates with subtle bugs or misunderstood requirements, it's reasonable to not want it regardless of copyright concerns.