My experience with Ada is you have legacy code bases and yes, forking these will continue for the next 30 years for similar products. But would anyone in 2019 r

My experience with Ada is you have legacy code bases and yes, forking these will continue for the next 30 years for similar products. But would anyone in 2019 really choose Ada for a design start in a DoD/aerospace realtime embedded system or cybersecurity application? I doubt it. It's hard enough to find developers in "common" languages. I think its very telling that real-world JOVIAL code bases are being converted to C, not Ada. Ada was supposed to replace JOVIAL. http://www.semdesigns.com/Products/MigrationTools/JOVIAL2C.html http://www.semdesigns.com/Products/MigrationTools/JOVIAL2C.h... There are also tools to convert Ada to C/C++/Java: https://www.mapusoft.com/ada-to-c-changer/ https://www.mapusoft.com/ada-to-c-changer/ I'd start any new embedded system in C or C++ with an appropriate coding standard, static analysis checks, and perhaps run-time ones. No way I would consider Ada. Maybe someday Rust will penetrate more, but it has a ways to go.