3 ms·
> by not intervening he essentially endorses that getting rust into the kernel requires consensus from all subsystem maintainers And let's not be obtuse, some
by gary_0 2y ago
> by not intervening he essentially endorses that getting rust into the kernel requires consensus from all subsystem maintainers
And let's not be obtuse, some of those subsystem maintainers are staunchly opposed, so "it's up to them" is obviously an indirect way of saying "no rust". I don't blame those maintainers for balking at a whole new very different language, but Torvalds has a choice of telling them either "suck it up, buttercup" or "I hear you; rust is gone". Instead, he's just letting things fester.
- chikere232 2y agoThis seems like black and white thinking. There's a huge spectrum between > "suck it up, buttercup" or "I hear you; rust is gone". where various levels of compromise happens. Maintainers are people and people can change their mind over time. If rust was a huge success in large parts of the kernel and you still had a few holdouts, sure, you could tell them to adapt or go away. In this early stage, it's kinda up to rust people to show that both they and rust can work in this setting