![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://fry.gs/pictrs/image/c6832070-8625-4688-b9e5-5d519541e092.png)
You live in a fantasy world if you think it’s possible to catch 100% of mistakes internally.
Nice strawman. No one said anything about catching 100% of mistakes internally. But outsourcing that work to unpaid volunteers with zero verification of qualifications is the definition of “passing the buck”.
The correct answer is to hire and train up a QA team.
Long time “old-school” kernel maintainers don’t know Rust and don’t want to learn Rust (completely fair and reasonable). But some of them don’t want to work with the Rust guys for lots’o’technical reasons.
It’s by far not an easy situation technically. Like this is a huge challenge.
But some of those old-school C guys are being vocal about their dislike of Rust in the kernel and gatekeeping the process. This came to a head at a recent conference (Linux Plumbers Conference?) and now one of the Rust maintainers has quit.
The big technical challenge is being confounded by professional opinions.