| > Headwinds from Apple, who are indifferent to the project, stingy with documentation, and not inclined to reduce their own rate of change. That is part of the challenge he chose to take on. > Headwinds from users, because of the stripped down experience. Users can be ignored. How much you get users to you is your own choice. > Headwinds from the kernel team, who are in the unenviable situation of having to accept and maintain code they can't test for hardware they don't own You don't have to upstream. Again, it's not the kernel team that chose to add support for "hostile" hardware so don't try to make this their problem. > and who apparently have some sort of schism over rust support? Resistance when trying to push an entirely different language into an established project is entirely expected. The maintainers in question did not ask for people to add Rust to the kernel. They have no obligation to be welcoming to it. > Be a heck of a lot easier if at least one of them was on your side. Except for the users all the conflicts are the direct result from the choice of work. And the users are something you have to choose to listen to as well. |
Their boss, however, did ask for it, so yes, they do have an obligation to be welcoming to it.