F-35 Fighter Jet's C++ Coding Standards [pdf]
Posted26 days agoActive26 days ago
stroustrup.comTech Discussionstory
informativeneutral
Debate
20/100
ProgrammingConventional_commitsAerospace Software
Key topics
Programming
Conventional_commits
Aerospace Software
Discussion Activity
Very active discussionFirst comment
6m
Peak period
25
0-1h
Avg / period
5.2
Key moments
- 01Story posted
Dec 7, 2025 at 4:34 PM EST
26 days ago
Step 01 - 02First comment
Dec 7, 2025 at 4:40 PM EST
6m after posting
Step 02 - 03Peak activity
25 comments in 0-1h
Hottest window of the conversation
Step 03 - 04Latest activity
Dec 8, 2025 at 4:15 AM EST
26 days ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 46185393Type: storyLast synced: 12/7/2025, 9:50:12 PM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
ADA/SPARK already owns this space.
This is also why car makers name their cars things like "Jeep Expedition" or "Ford Escape". The name doesn't change the car, but it does make it more exciting.
Or do you think the expectation was something more reasonable, like using this document as a tool to configure linting tools so that developers could get realtime feedback as they code?
If anything, the enemy will be defeated before they have had the time to understand the document in case it gets leaked xD
These days they are even more comfortable using C++ than they were back then due to improvements in process, tooling, and language.
A large segment in this article (which is great overall) focuses on this decision. The short summary is "hiring Ada developers was hard and middleware and tooling were difficult to acquire."
While I've moved through a lot of parts of the software industry and may just be out of touch, I actually feel that this may be less the case today. I've seen a lot of school programs focus less on specific languages and frameworks and more on fundamental concepts, and with more "esoteric" languages becoming popular in the mainstream, I actually think hiring Ada developers would be a lot easier today (plus, big industry players like NVIDIA are back to using Ada since AdaCore have been so effective at pushing SPARK, which probably helps too).
> (12) Multiply paper work in plausible ways. Start duplicate files.
> (13) Multiply the procedures and clearances involved in issuing instructions, pay checks, and so on. See that three people have to approve everything where one would do..
> (14) Apply all regulations to the last letter.
[1] https://www.cia.gov/static/5c875f3ec660e092cf893f60b4a288df/...
[1] https://en.wikipedia.org/wiki/Lockheed_Martin_F-35_Lightning...
The obvious expectation here is that these rules would be incorporated into some kind of automated linting tool.
I really need to get the fuck out of this industry.
> MISRA-C was used as the basis for the C applications and a coding standards was developed with the assistance of Bjarne Stroustrup, original author of the C++ language. For both C and C++ Static Code Analysis (SCA) tools are used to ensure that restricted features are not utilized. Arguments about the lack of reliability in either C or C++ are addressed by programming standards restrictions and SCA checks. In truth, this approach is probably more consistent and robust than the manual checks used for previous development efforts including Ada.
But C/C++ certainly did well enough for Lockheed Martin considering it's now one of their principal languages, if not the principal.
I’m a TS + Java person. Is this specific to C++ or is it just due to control freaks with low abstraction skills?