The Zig programming language has updated its code of conduct to ban LLM-generated code, vulnerability research, text-generation, and about anything AI at all

[chebra@mstdn.io]

@johan_andersson I think that was backwards, Bun started the rewrite because of the new Zig code of conduct. And it's going "great", 1M line PR, thousands of unsafe blocks, good luck to anyone trying to work with that...

[sesamzoo@mastodon.social]

@chebra @johan_andersson That 1M line PR missed at least one line. The README.md still says: "It's written in Zig" ‍️

bun/README.md at 2629789a22bd9fcd5137dc42d8a1865870aa992f · oven-sh/bun

Incredibly fast JavaScript runtime, bundler, test runner, and package manager – all in one - bun/README.md at 2629789a22bd9fcd5137dc42d8a1865870aa992f · oven-sh/bun

GitHub (github.com)

[kdwarn@social.coop]

@johan_andersson @campuscodi predates the port, so nothing to do with it.

[johan_andersson@mastodon.social]

@chebra Ah, if that's the order of event that's equally funny, heh.

[sesamzoo@mastodon.social]

@kdwarn @johan_andersson @campuscodi The policy gained at least a few paragraphs after Bun's fork of Zig.

https://youtu.be/1zBrQFpbK1U

Haven't checked, though, whether they were added before Bun's port to Rust.

[eestileib@tech.lgbt]

@corpsmoderne @johan_andersson @campuscodi

Rust has lisp-sized social problems as far as I can tell.

[theeclecticdyslexic@mstdn.social]

@campuscodi Ya, this is it... the bottleneck isn't how many merge requests they get, it's their ability to review them. Every merde request (not a typo) is time taken away from actually developing zig.

I don't see why so many other projects haven't figured this out yet. We don't need more merde requests for, we need to be able to read the merge requests we do get.

Banning AI is a crude way to do this, but unless someone wants to start paying for armies of reviewers to sort the slop...

[chazh@mastodon.social]

@johan_andersson @chebra It’s even funnier if you look at it as “Anthropic, the AI company that owns Bun, are desperately trying to get rid of a dependency on a language that puts limits on contributions that use AI.” Or it may be marketing genius if they actually pull it off, I don’t know.

[blindy@convo.casa]

@campuscodi Pretty sure that GitHub will probably do the same thing soon or later.

[gryphonmyers@mastodon.social]

@campuscodi They've had a no-AI policy for quite some time. Did anything about the policy change, or is it just getting more coverage because of the interview?

[sythys@chaos.social]

@campuscodi I guess I learn zig.

[beggarmidas@mastodon.social]

@campuscodi May not be a wise move on the vulnerability scanning. That's almost certainly gonna come back to bite him on his butt.

[malin@dice.camp]

@campuscodi
The language is so safe you can't even read an article about it.

[azuaron@cyberpunk.lol]

@campuscodi Bun--acquired by Anthropic--just had a huge, ridiculous PR opened to switch from Zig to Rust.

Perhaps Anthropic tried to purchase Zig, and was told to pound sand?

[azuaron@cyberpunk.lol]

@theeclecticdyslexic @campuscodi Oh, no, what you're supposed to do is have the slop machines review the PR.

I'm not joking. That's literal the thought process.

[dalias@hachyderm.io]

@campuscodi I love how the domain it's dealt with in is code of conduct.

[tris@chaos.social]

@campuscodi Do the same for horse64 @ell1e

[ell1e@hachyderm.io]

@tris @campuscodi if you have a proposal of how this should be expanded, let me know: https://horse64.org/docs/How%20to%20Contribute#why-ai-contributions-are-not-allowed

[laund@wetdry.world]

@eestileib @corpsmoderne @johan_andersson @campuscodi what does that mean?

Both "what does it mean for a (social?) problem to be lisp-sized" and "what did you want to communicate with that post"?

[zygoon@fosstodon.org]

@campuscodi next they will ban anyone using Dvorak to make patches.