Imagine if Ford mandates its suppliers to use Rust for the software in its car and it faced little problems after a few years out on the road.
Imagine if Ford mandates its suppliers to use Rust for the software in its car and it faced little problems after a few years out on the road.
The problem with aerospace, automotive, etc. is that there's substantial physical risk associated with errors. So there's not a lot of incentive to go with something brand new. Things like network security, etc. are a place where people are maybe a bit more concerned about safety than in some other areas, but also need performance, and notions of risk are more vague.
The interest of Tor developers in Rust is not surprising to me at all, for example.
Nothing is going to happen overnight, and I don't see C/C++ going anywhere, but I wouldn't be surprised at all to see Rust gaining a foothold in certain places, and expanding from there. I could also see it being a flash in the pan too, but it's unpredictable really.
Which is fine, nothing wrong with Ada.
You might be interested in some publicly available coding standards for the Joint Strike Fighter (C++) and the NASA JPL (C):
See: http://blog.regehr.org/archives/213 (particularly part 3)
http://blog.llvm.org/2011/05/what-every-c-programmer-should-...