Isn’t it reasonable for a maintainer to say “no rust here” when they don’t know rust, don’t want to learn it, and have decades of experience in C, and are maintaining that part of the system
The project has said it is a goal to move to a dual language model. So, no, it is not reasonable.
What would be reasonable would be technical arguments or pragmatic logistical concerns with the goal of finding solutions. What would be reasonable would be asking for and accepting help.
None of the reasonable stuff is happening. So, it not reasonable.
Isn’t it reasonable for a maintainer to say “no rust here” when they don’t know rust, don’t want to learn it, and have decades of experience in C, and are maintaining that part of the system
The project has said it is a goal to move to a dual language model. So, no, it is not reasonable.
What would be reasonable would be technical arguments or pragmatic logistical concerns with the goal of finding solutions. What would be reasonable would be asking for and accepting help.
None of the reasonable stuff is happening. So, it not reasonable.
Yes.
But that’s not what’s happening here. The guy who said no is not the maintainer of the rust code, and is not expected to touch the rust code at all.