There is no chicken-and-egg problem because the OS already does color management to map your source color space (sRGB, mostly) to your target monitor's color space. If it didn't, you wouldn't be able to view sRGB content correctly on wide-gamut monitors, for example.
The real challenge is in developing display backlight and phosphor technology to reproduce colors outside of the standard gamuts.
Or I can have the candidate code with me for an hour during the interview, and save $100. They get to ask me questions about the problem directly, and I can see where they are struggling, and how they debug (trial and error? Google/SO?)
RAD use rANS for their compressors. See ryg's blog [0] for more details, and a bunch more interesting posts about compression and various low-level optimizations.
I realize that this comment is tongue-in-cheek, but the reality is that Alphabet is a corporation, not a research university. Corporations by definition need to ship and make money.
It shouldn't be an issue given that HLL is approximate and that relatively few votes are undone. You could also debounce the vote before recording it in the counter, at the cost of a small delay.
Riemann is a generic event processor. You can use it to generate alerts or aggregate metrics, but you still need something like collectd or telegraf to collect system/app stats from each machine and send it to Riemann.