Rambling

Posted Feb 2, 2025 21:40 UTC (Sun) by andy_shev (subscriber, #75870)
In reply to: Rambling by Cyberax
Parent article: Resistance to Rust abstractions for DMA mapping

Ah, and for your second question: It doesn't work like this. It's they who came to the project and not him who went to Rust and telling them about their project. See the difference?

Rambling

Posted Feb 2, 2025 21:44 UTC (Sun) by Cyberax (✭ supporter ✭, #52523) [Link] (3 responses)

Why doesn't it work? C developers who disagree are free to fork the kernel and make a "Veteran C Developer" project.

Rambling

Posted Feb 3, 2025 9:12 UTC (Mon) by andy_shev (subscriber, #75870) [Link] (2 responses)

Because it's a newcomer's responsibility to follow the (established) rules of the project, and not otherwise.

Rambling

Posted Feb 3, 2025 9:14 UTC (Mon) by intelfx (subscriber, #130118) [Link] (1 responses)

So far, “rules of the project” are that Rust is greenlit as an experiment.

Rambling

Posted Feb 3, 2025 12:29 UTC (Mon) by andy_shev (subscriber, #75870) [Link]

Yes, and not only technical experiment. Seems social part of it is not less interesting.

Rambling

Posted Feb 5, 2025 5:44 UTC (Wed) by ssmith32 (subscriber, #72404) [Link] (1 responses)

The kernel is as much "their" project as it is his.

He maintains a key part of the project, but relative to the kernel as a whole, it's a small part.

He's not Linus, and he's certainly not Greg. It's not his project.

Rambling

Posted Mar 2, 2025 20:28 UTC (Sun) by andy_shev (subscriber, #75870) [Link]

The first statement is an obvious mistake. The Rust thingy is way too young in comarison to the Linux kernel project (and even younger if you look at the first considerations to use Rust inside Linux kernel).
The last statement is also false. LK is the project of the community, and it is his project as well as Linus' or Greg's.