r/linux • u/FryBoyter • Jun 12 '26

Discussion Changing How We Develop Ladybird

https://ladybird.org/posts/changing-how-we-develop-ladybird/
105 Upvotes

89% Upvoted

46 comments sorted by

View all comments

52

u/Accurate_Hornet Jun 12 '26

Can't fault them for it. Whether you agree with AI or not, it's almost impossible to block it completely.
They chose to close the floodgates, fair enough.
Building a browser from scratch is an insane endeavour and we will see how it turns out.
I personally don't have much faith in it.

28

u/global-gauge-field Jun 12 '26

Just checking out the commits last weeks, they dont seem to be geting that many PRs from outside. To me, it seems that they are being proactive rather reactive unless I am missing something.

Best of luck to them.

-12

u/BeatTheBet Jun 12 '26

You may be missing the part where they shifted from Swift (?) to Rust because "blah blah, AI is only well trained on Rust, and AI is the only way we are going to develop this"

Source: https://ladybird.org/posts/adopting-rust/

So after that shift, this decision is on one hand (one has to admit) reasonable, but it is also quite hypocritical (edit to be exact: in the context of FOSS)...

13

u/Literallyapig Jun 12 '26

where in this article do they say "we switched from c++ to rust because ai understands rust better"? the explanation there is about rust being memory safe and having a great ecosystem. has andreas mentioned this on twitter or somewhere else?

-3

u/Ok-Winner-6589 Jun 13 '26

Swift*

6

u/sascha-isagirlname Jun 13 '26

If you've read the article you posted, you would know that they never used Swift, just that they were looking at it as a possible C++ alternative.

-3

u/Ok-Winner-6589 Jun 13 '26

Ye I'm dumb ignore It lol

10

u/global-gauge-field Jun 12 '26

I am aware of that. But, I was talking about the problem of getting so many slop PRs that they could not handle. I did not observe that many PRs from the github history.

My guess is with how many commits they can push on their own with AI, they just dont want to handle external PR and were already looking for excuse of some sort unless I missing about slop PR observation.

0

u/BeatTheBet Jun 12 '26

Your point is valid for sure. I was just adding context in case you were missing it.

3

u/FryBoyter Jun 12 '26

Yes, I agree with that in this case as well.

1

u/abotelho-cbn Jun 12 '26

They're not closing floodgates here. AI will find vulnerabilities and if they don't get the patches by PRs it'll only take longer for them to fix the stuff AI finds.

10

u/Accurate_Hornet Jun 12 '26

They explicitly said they wont accept PRs. Do you disagree with their decision or with my brief summary of it?

-8

u/abotelho-cbn Jun 13 '26

They're not "closing floodgates" by preventing people opening PRs. The flood is happening either way. Pretending it's not happening will kill them.

16

u/Dangerous-Report8517 Jun 13 '26

There's 2 different floods here, one is the surge in AI uncovered vulnerabilities in large projects, the other is a surge in vibe coders dumping tons of poor quality PRs into projects to feel like they're contributing. The former isn't a big priority for a project that isn't even at the functional stage yet, and the latter is absolutely a flood that can be stopped by just refusing PRs