Embedded developers face a growing choice of programming languages. Five recommendations are offered for selecting the right one: avoid dead or dying languages (like Assembly and LabVIEW), prefer object-oriented languages, use only standardized languages to minimize technical debt, balance runtime weight (e.g., MicroPython's 300–400KB interpreter vs. C/C++'s near-zero overhead), and ultimately choose what fits your team's actual needs. C++ is suggested as a strong default, while C is characterized as aging and Rust as not yet standardized enough for most commercial projects.
Table of contents
Recommendation #1 – Avoid Dead or Dying LanguagesRecommendation #2 – Select Object-Oriented LanguagesRecommendation #3 – Use Standardized Languages OnlyRecommendation #4 – Balance the Languages Run-time WeightRecommendation #5 – Use the Language that is Right for YouConclusions5 Impressions