Just to say it clearly because I think it´s interesting: The Varig-Flight seems to have suffered of a decimal point error in the flight plan, not on a 7-segment display.
Obviously yes, but the fact that decimal points are
already dangerous, the typical 7-segment display making them very small replicates that danger. There are solutions to this, for example making the decimal point bigger, brighter, adding dead space in the
correct place (i.e., where the point is), or showing the digits after the decimal point in smaller fonts (i.e., using smaller 7-segment displays for decimal part, but then you need fixed decimal point location, which isn't a bad idea), and the article discusses most of these points, if you read it.
One thing which is unavoidable and unsolvable in 7-segment displays is addition of "random" spaces around number 1 (you can choose which side it is added to, but if you do it dynamically, users are even more confused). That acts as a mental separator (thousands or decimal), want it or not. Now if this is your only problem, then fine, but add this to poor design choices like a very small decimal dot, driven too dimly, and switching the place of the dot dynamically to any unexpected place, and the likelihood to read it wrong is even larger than on a paper - and even on paper, decimal points are sometimes read wrong.
I suggest everyone who engineers physical user interfaces reads the paper, even if they end up preferring 7-segment displays. People who get offended by the clickbaity title should just ignore the title. (I would have preferred "7-segment displays considered harmful".)