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.
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.
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.