2 ms·
You're wrong. The only real exception is the code in airplanes, failures for which can cause loss-of-life (e.g. Jet ECUs, fly-by-wire). Even then, in some cas
by aidenn0 9y ago
You're wrong. The only real exception is the code in airplanes, failures for which can cause loss-of-life (e.g. Jet ECUs, fly-by-wire). Even then, in some cases, the solution is not correct software, but a hardware fail-safe.
Everything else is pretty much programmed like this. I've seen things you'd likely describe as "deeply embedded" running a CORBA server so that Java written by one company can communicate with C++ written by another company, integrated by a third company that doesn't have the source to either.
Some automotive software is starting to show some trends towards the airplane approach, but the big exception among safety-critical parts is self-driving cars. Many of them even use ML algorithms for which it is non-trivial to even determine why a particular error was made.
Cost is a big driver of this. Given equally competent programmers, creating formally correct software is 1-2 orders of magnitude at low levels of complexity. Current software-engineering indicates that the difference increases as complexity increases. You can easily end up spending 100x as much for software that has 1% as much complexity.
Much of the time, features drive sales, and sales drive revenue, so the less rigorous software ends up with both higher budget and lower costs.