Choosing among them.
WHAT C PROVIDES
Maximum portability and minimal footprint, with no safety.
WHAT C++ PROVIDES
Abstraction with control, at the cost of complexity.
WHAT GO PROVIDES
Simplicity, fast builds and easy concurrency, with garbage collection.
WHAT RUST PROVIDES
Memory safety and performance, at the cost of a learning curve.
WHAT TO CHOOSE FOR EMBEDDED AND CONSTRAINED ENVIRONMENTS
C, usually, or Rust where the toolchain supports it.
WHAT TO CHOOSE FOR NETWORK SERVICES
Go, for most teams, unless requirements demand otherwise.
WHAT TO CHOOSE FOR PERFORMANCE-CRITICAL WORK WITH SAFETY REQUIREMENTS
Rust.
WHAT TO CHOOSE WHEN AN ECOSYSTEM DEMANDS IT
Whatever that ecosystem uses. Game engines and scientific libraries frequently decide for you.
WHAT TO WEIGH
Team experience, which matters more than language merit Hiring Compilation times, which affect daily productivity
Deployment: static binaries simplify operations considerably
WHAT NOT TO DO
Choose a systems language for work that does not need one.
WHY
The productivity cost is real, and most applications are not performance-limited by their language.
