being new does not mean you do not have the right to develop the same way everybody else is. they did not start these issues, there were C people causing issues for no reason other than not liking rust that started it.
Have you actually read the reasoning behind the anti-rust? it has absolutely nothing to do with it being rust. They would have just as many issues with it if it was Go instead.
I have seen the reasoning they are actually presenting, and it is just various versions of “but I don’t want this to be here” even though they have the option of not interacting with it. nobody is forcing maintainers to support rust code in the thing they maintain, they just can’t prevent rust code from interfacing with it. their arguments are based purely on not wanting to interact with rust but they don’t have to, so they are wrong to block it.
The issue is with creating more work for others. Supporting a multi-language toolchain and build environment is a lot more work than a single language one. The R4L folks have made it their mission to shoehorn Rust into the kernel and they’ve explicitly stated that they will not avoid making more work for others. This has upset some longterm maintainers who did not sign up for additional workload.
Linus Torvalds has been accused of many things but he has always been loyal to his best maintainers. That’s been a big key to his success.
yeah fuck those entitled Rust Developers.
yeah how dare they want to develop in the same way that everyone else does
they should have been a bit more respectful to the C maintainers and devs, as they were the newcomers.
They were pretty respectful, it was the C-devs that were at fault
being new does not mean you do not have the right to develop the same way everybody else is. they did not start these issues, there were C people causing issues for no reason other than not liking rust that started it.
Have you actually read the reasoning behind the anti-rust? it has absolutely nothing to do with it being rust. They would have just as many issues with it if it was Go instead.
I have seen the reasoning they are actually presenting, and it is just various versions of “but I don’t want this to be here” even though they have the option of not interacting with it. nobody is forcing maintainers to support rust code in the thing they maintain, they just can’t prevent rust code from interfacing with it. their arguments are based purely on not wanting to interact with rust but they don’t have to, so they are wrong to block it.
The issue is with creating more work for others. Supporting a multi-language toolchain and build environment is a lot more work than a single language one. The R4L folks have made it their mission to shoehorn Rust into the kernel and they’ve explicitly stated that they will not avoid making more work for others. This has upset some longterm maintainers who did not sign up for additional workload.
Linus Torvalds has been accused of many things but he has always been loyal to his best maintainers. That’s been a big key to his success.
Aw hell naw, torvalds supports rust in the kernel and the hate against it is just not based on reality
Sure he allows rust now in the kernel.org but I thought you were referring to the drama around Hector Martin.
The drama where he ended up ripping into the maintainer who’s trying to block rust code from being added? :P