No resistance to change?

Eh, not really. That kinda was the whole point of this "experiment" [1].

To me the more salient questions are how long before (a) we get Rust in a core subsystem (thus making Rust truly _required_ instead of "optional unless you have hardware foo"), and (b) requiring Rust for _all_ new code.

There is no point in half-measures; those only result in higher costs and fewer benefits.

[1] As the saying goes, "It's only temporary if it doesn't work"