[pelasaco]

What’s the point? People will just fork it and improve it with AI anyway. In another hand, it would be an interesting experiment to watch how the original and the fork diverge over time. Especially in terms of security discoveries and feature development.

[sph]

Go ahead, we're all still waiting for these "AI-improved" projects to appear.

Meanwhile I'll keep using SDL from the official maintainers which have been working on it for decades.

[pelasaco]

> Meanwhile I'll keep using SDL from the official maintainers which have been working on it for decades.

That's just Virtue signaling.

"AI-improved" projects like "rewrite $FOO in rust" are popping up everywhere. I dont support it, sqlite3 being rewritten in rust makes me just sad https://turso.tech/blog/introducing-limbo-a-complete-rewrite..., but this "$PROJECT bans AI" is just ridiculous. Ideally we should try to use it for the good, instead of ban it.

[xxs]

> "$PROJECT bans AI" is just ridiculous

why so? If they don't feel like reviewing code (or ensure copyright compliance) they are free to reject that.

If you feel strong about it, go fork and maintain it on your own.

[orwin]

I think you don't understand how tiring it is to review full-llm code. I think banning it temporarily until people calm down with AI-generated PRs is a very sane solution. If it is still the solution in 3 years, maybe you would have a point then.

I only manage 3 'new' hires and I am of the mind of banning AI usage myself despite my heavy usage (the new hires don't level up, that's my main issue now, but the reviewing loops and the shit that got through our reviews are also issues).

[LLMCodeAuditor]

I am not sad about rewriting sqlite in Rust because this is the third such attempt I've seen, and just like the other two it looks like this project is totally doomed: https://github.com/tursodatabase/turso/

Like, look: https://github.com/tursodatabase/turso/issues/6412 It's stunning considering this project is advertised as a beta. There are hundreds of bugs like this. It's AI slop that gets worse the more AI is thrown at it.

SDL is 100% correct to keep this AI mess as far away from their project as possible.

[raincole]

I'm pretty pro-AI, but I find it very amusing that every single time an open source project enacts no-AI policy, someone will chime in and explain how it will be outcompeted by the yes-AI version, while in reality it never happens.

[pelasaco]

> while in reality it never happens.

it never happens in 3 weeks? The AI revolution is just starting.. too soon to jump in conclusions, i guess?

[skydhash]

Make it to 2 or more years. That’s the amount of times that I’ve been seeing comments equating not using AI with hopelessly doomed project/career.

[pelasaco]

I am sure you noticed how fast the things started to change since the beginning of 2026 right? In terms of tooling, model, context, pricing, etc?

[thunderfork]

This is also something we've all been hearing for ages. "<Model version>/MCP/agents/yadda yadda are totally like anything that's come before!"

[pelasaco]

> "<Model version>/MCP/agents/yadda yadda are totally like anything that's come before!"

and they are right. We never saw that before. That's why we all fear it.

[ethin]

Huh? I've been seeing the "hopelessly doomed because of AI" trope practically since ChatGPT came out. It wasn't even remotely as bad as it is now, but it's been there all along.

[arnvald]

Will they? Will someone have enough time, skill and dedication to maintain it? I don’t think using AI will by itself make a big enough difference, it’s still a lot of work to maintain a project

[pelasaco]

> I don’t think using AI will by itself make a big enough difference, it’s still a lot of work to maintain a project

I think you are wrong. The "a lot of work maintaining a project" would be reduced, specially issues investigation, code improvement, security issues detection and fixes. SDL isn't a that relevant project, but "ban AI-written commit" - which reading the issue, sounds more like ban "AI usage" - is counterproductive to project.

[skydhash]

> SDL isn't a that relevant project,

SDL is kinda the king of “I want graphic, but not enough to bring a whole toolkit, or suffer with opengl”. I have a small digital audio player (shangling m0) where the whole interface is built with SDL.

[spookie]

> SDL isn't a that relevant project

Unreal 5 uses SDL to be able to create "windows" in a cross platform manner (specific use case, but not just a thing on Linux [1]). Many others do as well.

[1] https://dev.epicgames.com/documentation/unreal-engine/updati...

[krapp]

>SDL isn't a that relevant project

Many, many things use SDL. It's one of those bottom pieces in the Jenga tower of infrastructure dependency[0].

Not maintained by some random person (that would be Sean Barret's STB library) but still, it seems irrelevant only because it's already ubiquitous.

[0]https://xkcd.com/2347/

[nottorp]

> and improve it with AI anyway

No. My impression is that most AI PRs aren't made to improve anything, but to inflate the requester's reputation as an "AI" expert.

> and feature development

There's also this misconception that more features == better...

[pelasaco]

there is no misconception here. Bug fixes, issue triage and feature implementation reduced time is a thing.

[nottorp]

The misconception is that new features are always necessary, not that it would be nice if they were done faster.

[ChrisRR]

If people want to fork at and work in their own manner then that's fine, but that doesn't mean you shouldn't protect the project that you're personally working on

[signa11]

don't mind if you do 'guv, don't mind at all.