Sure! There are a few major reasons:
- The built-in concurrency primitives are designed with real time systems in mind, freeing you from the need of constructing a cyclic executive and scheduling manually.
- The tools to deal with time constraints and diagnose why deadlines were not met are very high quality. The Ravenscar profile essentially guarantees that all scheduling decisions are known statically.
- Not strictly real time related, but
since real time systems are often safety priority systems I'll mention it anyway: Ada makes memory management hard to get wrong.
If you're interested, I think Programming Real-time with Ada 2005 over at Embedded.com[1] provides a really good overview. Many of those features are meant for safety critical hard deadline systems and are consequently overkill for bedroom experiments, but for those projects you can just take the default basics and get 98% of the way there.
(If the article seems outdated in some aspects, recall that there were some further imptovements to the standard in 2012.)
[1]: https://www.embedded.com/design/prototyping-and-development/...