Ada is a programming language with certain features:
Multi Paradigm.
Multi Level.
Imperative.
Procedural.
Strictly typed.
Statically typed.
Case insensitive. As in Function and function both mean the same.( Even FuNctIOn does)
Many Ada users choose it when the application must run quickly and safely.
The need for languages that promote reliability and simplify maintenance is well established. Hence, emphasis was placed on program readability over ease of writing.
Ada's Language Reference Manual
Ada is a great language to learn programming and programming techniques. It has all you can expect from a modern programming language. But it also has some really advanced features that can be interesting for more experienced programmers:
Concurrent Programming
Complete Object Oriented Programming.
Embedded Systems Programming. Such as Robotics or Avionics.
Real Time Systems Programming.
Distributed System Programming.
Functional Programming.
Multi-threading and Multitasking,
Synchronization
Resource Protection
Safety: The software must not harm the world.
Security: The world must not harm the software.
John Barnes - Safe and Secure Software
Developed for the Department Of Defense of the USA, it was originally designed to support the construction of long-lived, highly reliable software systems and real-time embedded systems .
Its design:
Emphasizes readability
Avoids error-prone notation
Encourages reuse and team coordination
Is efficiently implementable
A significant advantage of Ada is its reduction of debugging time.
These designed features optimize Ada to be a Language for very large programs. For Long Lived programs and systems, that spend most of their life cycle in maintenance. For robust programs with correctness, security, and reliability. For embedded systems with low level hardware control, concurrent tasks, and real time. Then again, can't hammer this enough, in a safe environment.
Ada tries to catch as many errors as reasonably possible, as early as possible. Many errors are caught at compile-time by Ada that aren't caught or are caught much later by other computer languages. Ada programs also catch many errors at run-time if they can't be caught at compile-time (this checking can be turned off to improve performance if desired). In addition, Ada includes a problem (exceptions) handling mechanism so that these problems can be dealt with at run-time.
Ada's user base has expanded far beyond the U.S. DoD to many other areas such as large-scale information systems, distributed systems, and scientific computation. Major Ada niches include aerospace and safety-critical systems.
Ada compilers can generate code comparable to C, C++, and Pascal compilers. Because of the way Ada was designed, Ada compilers can sometimes generate better code because they have more information that can be used for code optimization. For example, in a large number of cases an Ada compiler can do better than a C or C++ compiler can while passing parameters, because an Ada compiler knows when aliasing is not possible.
It is true that Ada run-time error-checking capabilities require some time and space, but they can be selectively or completely turned off. Since Ada compilers can often detect and optimize these away, they often do not have as much of a performance hit as you might expect even when left in.
Also, in a typical "pay for what you use" manner, if the compiler left it in... you probably want that. Let me explain: A typical... "optimization" in other languages is to turn off safety checks, which may accelerate 99% of uses by a nanosecond in those languages (say python, a very nice language that allows everything you throw at it), but then crash everything in 1% of use cases. Ada allows for control of these extreme phenomena by default, sometimes with no extra cost on time. It is part of the structure, so it does not take extra time to build it.
I usually compare it to a very interesting case in architecture: cathedrals. You may already know that cathedrals are really big. For that reason they need supporting walls on the sides of it, sticking out in right angles (like a T) from the load bearing walls. Architects from the middle ages would assume that any structural wall and load will need extra materials, and it grows exponentially. Then Ada uses these features of security structurally, not as added components sticking out, which is more like using steel beams. They increase security, but also allow components to compose linearly, not exponentially, with the size of your project, and they ensure integrity unreachable by the T-shaped walls of old.
Sometimes, out there in the field, it is a dogma that "C is the fastest/bestest/nicest language." and that everything else is worse. This dogma affects Ada specially. Performance wise, Ada is at the same level, safety wise Ada is superior. If you evaluate Safety and Performance, both: Ada is the clear winner. But like ancient masons watching the New York City skyline, some simply do not believe it. Trapped in dogma, they just assume the loadding walls must be there, hidden behind the pavement or maybe inside the glass, whith the moderns architects just rolling their eyes and getting back to work, advancing the industry as others try to catch up years or even decades later (TypeScript anyone?).
These tutorials prettend to show the actual capabilities of the Ada Language. If you still don't believe the structural power of Ada, keep reading: The proof is in the pudding.