Hacker News Reader

A slight inaccuracy: the flight strings are not x86, but ARM, running on a custom board.

Also, only the actual graphical display application uses Chromium/JS. The rest of the system is all C++. The display code has 100% test coverage, down to validation of graphical output (for example if you have a progress bar and you set it to X% the tests verify that it is actually drawn correctly).

View on HN

How stateless and independent is each display?

Can't say exactly re statelessness, but I would not be surprised if you could power-cycle all displays if needed in the middle of a mission.

As far as independent, completely independent from each other.

> but I would not be surprised if you could power-cycle all displays if needed in the middle of a mission.

Indeed you can, judging by the instruction to power off and clean all displays (then power them back on) prior to ISS rendezvous/docking in the live stream.

How is that done? By pixelwise comparison with a test image?

I'm curious about this as well. From what I remember chromium does what you suggest to verify what is rendered down to the pixel: https://developers.google.com/web/updates/2020/02/chromium-c...

Reply on news.ycombinator.com