[OopsCriticality]

Not OP but from the perspective of the industrial side: no track record, no formal standard, changes too fast, incomplete documentation, doesn't have an extensive commercial and supporting ecosystem (e.g. Parasoft, Java Path Finder), limited pool of experienced programmers with embedded and regulated environment experience. Arguably, it falls under the heading of "too new".

I'd prefer to deal with known knowns rather than the known unknowns or gasp unknown unknowns of something new. It's a very conservative position, but it's borne out of the expense associated with mistakes and corrections of.

[steveklabnik]

Cool thanks! I'm trying to figure out what blockers are so we can prioritize things; a lot of these are very reasonable, but not immediately actionable things for me. Sounds good. :)

[OopsCriticality]

Sorry I can't offer anything more specific and actionable; I guess comparing Rust to a fine wine, something that must be aged to reach full potential, will have to do :)

[steveklabnik]

Hehe, no need to be sorry. It's one of the best answers, actually: it means that there aren't any fires, it's just about playing the long game and letting time pass. I prefer that. :)