What time would SpaceNoodle allow? You’re in a thread about Kernel devs talking about contributing new code and why some new code is permissible, but other code, including C code, with fixes for C, are arbitrarily not allowed because it’s coming from a Rust dev.
With the “refactoring replaces old, working bugs, with new, untested bugs” mindset, you might as well stick with the good stuff from 50 years ago. Those bugs are very well-known.
The Linux kernel folks say that the rust folks missed the deadline for major code changes and the project is currently in minor bug fix mode prior to release. They weren’t prepared to accept thousands of lines of changes at this point on the grounds that introducing new regressions without time to fix them is a real risk. So timing is claimed to be an issue.
That’s an interesting perspective you got there. I hope you adopt the “ideological” mindset that adding fixes and memory safety is generally something you’d want, regardless of the language.
What time would SpaceNoodle allow? You’re in a thread about Kernel devs talking about contributing new code and why some new code is permissible, but other code, including C code, with fixes for C, are arbitrarily not allowed because it’s coming from a Rust dev.
With the “refactoring replaces old, working bugs, with new, untested bugs” mindset, you might as well stick with the good stuff from 50 years ago. Those bugs are very well-known.
The Linux kernel folks say that the rust folks missed the deadline for major code changes and the project is currently in minor bug fix mode prior to release. They weren’t prepared to accept thousands of lines of changes at this point on the grounds that introducing new regressions without time to fix them is a real risk. So timing is claimed to be an issue.
Who said this, and where? Are you sure you’re not throwing together the bcachefs stuff with this Rust topic?
Oh, I’m totally wrong and had mixed the two up, sorry.
Interesting that you ignore how they were just going to change things for ideological purposes, which was my entire point.
That’s an interesting perspective you got there. I hope you adopt the “ideological” mindset that adding fixes and memory safety is generally something you’d want, regardless of the language.