News for hackers. Stuff that matters.
Re:Joint Strike Fighter Air Vehicle C++ Coding Standards [pdf] by ncmncm on Sunday March 07, 2021 @02:49PM (#26379111)
(2005)

It is a very, very different language, today, than when this was composed.

Re:Joint Strike Fighter Air Vehicle C++ Coding Standards [pdf] by austinprete on Sunday March 07, 2021 @11:25PM (#26382282)
Definitely worth noting the year, but I’d be fairly surprised if the standards for real-time avionics software changed much since then. I’d guess they still stick to a small subset of the Goliath that is C++
Re:Joint Strike Fighter Air Vehicle C++ Coding Standards [pdf] by ncmncm on Monday March 08, 2021 @12:44AM (#26382626)
Most of the Goliath results in faster, safer, more reliable code. By design.

Avoiding new features means slower, unsafe, less reliable code. At the extremum, in this direction, is the C subset that (e.g.) Linux and BSD kernels wallow in.

Re:Joint Strike Fighter Air Vehicle C++ Coding Standards [pdf] by 6pac3rings on Monday March 08, 2021 @07:52AM (#26385155)
The LM Goliath needs to put up actual performance figures under scientificly rigorous scrutiny for comparison to substantiate those claims against enthusiast driven technology (not marketing, PR) or shutup. And, factor in dollars a bang for every block of technical excellence performing in the source code.