3 ms·
Filho's exit message had this point: Lastly, I'll leave a small, 3min 30s, sample for context here: https://youtu.be/WiPp9YEBV0Q?t=1529 -- and to reiterate
by nabla9 2y ago
Filho's exit message had this point:
Lastly, I'll leave a small, 3min 30s, sample for context here:
https://youtu.be/WiPp9YEBV0Q?t=1529 -- and to reiterate, no one is trying force
anyone else to learn Rust nor prevent refactorings of C code.
First comment to this article is insightful.
>The “file system maintainer” had a more legitimate question than most comenters have allowed. Under Linus’s rules for maintainers, when an intrface is changed it is the responsibility of the person requesting the change to submit patches for all other uses of the interface. That requires the “filesystem maintainer” to patch Rust code – which he is unqualified to do. That means he can no longer change any interface, which is a big change in Linux policy that Linus would need to address.
It seem that Filho is not correct in his statement. There must be policy change or maintainers must be forced to learn Rust.
- Bluestein 2y agoInteresting. Nice catch. It would stand to reason that the language choice would "cascade", turning into a de facto pre requisite ...
- steveklabnik 2y ago"You need to fix up stuff you break" is the norm, but given that Rust for Linux is an experiment, it is explicitly an exception to this.