3 ms·

I'm afraid the full quote is too long to be a title for an HN article. I think my title accurately reflects the author's sentiment. The precise quote is: > B

I'm afraid the full quote is too long to be a title for an HN article. I think my title accurately reflects the author's sentiment. The precise quote is: > Behold, a Linux maintainer openly admitting to attempting to sabotage the entire Rust for Linux project: Please also feel free to read the post, and the underlying LKML messages. EDIT: I posted the wrong link. HN will not allow me to modify the link location. Sorry about the confusion. The correct link is: https://social.treehouse.systems/@marcan/113941358237899362 https://social.treehouse.systems/@marcan/113941358237899362

bangaladore 2y ago
The linked comment is not from the author you are quoting, as far as I can tell.
- mustache_kimono 2y ago
  I had two links open and pasted the wrong link. This is the correct link: https://social.treehouse.systems/@marcan/113941358237899362 https://social.treehouse.systems/@marcan/113941358237899362 Sorry for the confusion!
colingauvin 2y ago
Here is the content of the page you linked: >On Wed, Jan 29, 2025 at 10:33:22PM +0100, Danilo Krummrich wrote: > I accept that you don't want to be involved with Rust in the kernel, which is > why we offered to maintain the Rust abstraction layer for the DMA coherent > allocator as a separate component (which it would be anyways) ourselves. >Which doesn't help me a bit. Every additional bit that the another language creeps in drastically reduces the maintainability of the kernel as an integrated project. The only reason Linux managed to survive so long is by not having internal boundaries, and adding another language complely breaks this. You might not like my answer, but I will do everything I can do to stop this. This is NOT because I hate Rust. While not my favourite language it's definitively one of the best new ones and I encourage people to use it for new projects where it fits. I do not want it anywhere near a huge C code base that I need to maintain. You have either pasted the wrong link, or are editorializing the title.
- mustache_kimono 2y ago
  I had two links open and pasted the wrong link. This is the correct link: https://social.treehouse.systems/@marcan/113941358237899362 https://social.treehouse.systems/@marcan/113941358237899362 Sorry for the confusion!

bangaladore 2y ago

The linked comment is not from the author you are quoting, as far as I can tell.

mustache_kimono 2y ago
I had two links open and pasted the wrong link. This is the correct link: https://social.treehouse.systems/@marcan/113941358237899362 https://social.treehouse.systems/@marcan/113941358237899362 Sorry for the confusion!

colingauvin 2y ago

Here is the content of the page you linked: >On Wed, Jan 29, 2025 at 10:33:22PM +0100, Danilo Krummrich wrote: > I accept that you don't want to be involved with Rust in the kernel, which is > why we offered to maintain the Rust abstraction layer for the DMA coherent > allocator as a separate component (which it would be anyways) ourselves. >Which doesn't help me a bit. Every additional bit that the another language creeps in drastically reduces the maintainability of the kernel as an integrated project. The only reason Linux managed to survive so long is by not having internal boundaries, and adding another language complely breaks this. You might not like my answer, but I will do everything I can do to stop this. This is NOT because I hate Rust. While not my favourite language it's definitively one of the best new ones and I encourage people to use it for new projects where it fits. I do not want it anywhere near a huge C code base that I need to maintain. You have either pasted the wrong link, or are editorializing the title.

mustache_kimono 2y ago
I had two links open and pasted the wrong link. This is the correct link: https://social.treehouse.systems/@marcan/113941358237899362 https://social.treehouse.systems/@marcan/113941358237899362 Sorry for the confusion!