You can think of the Rust Editions as updates to the language, that would break compatibility with previous versions. But the key here is, that you can mix crates with older versions and the new one in one project and cargo will figure out which one to use for each crate (based on the cargo.toml file). That means breaking changes without breaking compatibility of existing libraries and crates, unlike in other languages.
In such a case I would post to the mailinglist in the main post link, and in the post content a secondary link to the comment section of Phoronix article directly.
Forking does not solve the problem, it escapes it. The problem in the main Rust Kernel will stay, not working together, arguing, while the fork might work for those who work on the fork. This is not a driver or feature where they can fork, work on it separately. It completely misses the point.
Forking does not solve the problem, it only escapes it. Its waste of time and effort in this case. The solution is that the devs work together. Otherwise it makes no sense to have Rust if no one works together. Discussion is the best way to handle this and to come to a solution. Its such an important topic that you have to discuss it, this is healthy, this is how it should be done. This is how its done.
There is no point in forking. The problem is not adding Rust to the Kernel, the problem is the C developers to get to work on it together. Forking does not solve this issue. Its not about proving being more efficient or not.
Why do you think its a problem that this is discussed a lot? Its a huge deal, so its only good its discussed and not accepted by everyone. I think this is healthy. We only read about the drama and a few quotes, but if you look closer then their argumentation makes a bit more sense. It is not just drama for the sake of drama. Some maybe toxic, that is another thing, because they would be toxic with other topics too.
Here is in a videoformat from ThePrimeagen (programmer at Netflix, or he was, not sure about current state) going through a recent discussion in the Linux Kernel mailing list about this topic. It's about a hour long and adds some thoughts on its own too, which was valuable to me. - https://www.youtube.com/watch?v=8QcQ_128OIw
Not bad is not a reason for people to upgrade. Something must be good, otherwise why would you. And there are couple of problems with Windows 11 like the bloat, less optimized on old hardware (if it runs) and all the headlines and talk about Microsoft integrating an Ai that scans everything you do. Plus the usual compatibility issues with updates and data collection that you can't turn off. In the end, its just annoying for people to upgrade to Win 11, without any benefits to them, but the risk of new problems and incompatibility.
However if I were a Possibly windows user who does not want to use anything else than Windows, then there is no question: upgrade is a must, because 10 stop getting support. Its as simple as that, provided the hardware can run it.
Debian famously debated between Upstart and systemd before ultimately adopting systemd in 2014. Once Debian made its decision, other distributions that had been considering Upstart also shifted focus toward systemd.
Debian was probably the biggest contributor in why Upstart failed.
What's the point of using Rust, if you don't want to think and program in Rust? If you seriously don't want to learn and deal with safe code and think every step of it in advance before compilation, then Rust is the wrong language for you. Either use a low level language like C and Zig, which gives you control over the system, but does not have a borrow checker. Or use a language with a runtime check that does this automatically for you without a borrow checker, like Go in example.
Finding good project names is one of the hardest things. It depends on the project, sometimes its just in front of you with play on words that has some meaning. It could be some historical reason why you name the project, or something out of blue with metaphorical meaning.
I usually think of a few words and then lookup in thesaurus for words with similar meaning, in example for the random word "management": https://www.wordhippo.com/what-is/another-word-for/management.html Its often fruitless, sometimes not. So its worth trying if you get stuck.
Well, its all there in the link and screenshot shows. The option is "Allow Github to use my data for Ai model training". At least I think this includes Copilot training, as far as I understand. The Privacy Statement link below specifically talks about Copilot:
Allow GitHub, its affiliates and third parties to use my data, including Prompts, Suggestions, and Code Snippets, for AI model training.
