> Even Samsung is running into this issue now [...]
These large corpos are so greedy to the point they harm themselves. I remember something similar with Amazon, where the Amazon shop had to redo the whole architecture from some microservice setup back to a monolithic approach because they used AWS and paid these weirdly structured prices like everyone else. Which made running a monolithic architecture under such constraints inherently cheaper. Not sure what the resulting compounded business cost for this "endeavor" was, but more often that not such things are never accounted for, so they don't show up as an issue.
If you have a large set of lets say floats in the range between 0 and 1 and you add them up, there is the straightforward way to do it and there is a way to pair them all up, add the pairs, and repeat that process until you have the final result. You will see that this more elaborate scheme actually gets a way more accurate result vs. simply adding them up. This is huge, because there is a lot of processing done with floats where this inherent issue is entirely disregarded (and has an impact on the final result).
Donald Knuth has all of that covered in one of his "The Art of Computer Programming" books, with estimations about the error introduced, some basic facts like a + (b + c) != (a + b) + c with floats and similar things.
And believe it or not, there have been real world issues coming out of that corner. I remember Patriot missile systems requiring a restart because they did time accounting with floats and one part of the software didn't handle the corrections for it properly, resulting in the missiles going more and more off-target the longer the system was running. So they had to restart them every 24 hours or so to keep that within certain limits until the issue got fixed (and the systems updated). There have been massive constructions breaking apart due to float issues (like material thicknesses calculated too thin), etc.
> It’s like saying sunglasses protect you from the sun
It is actually much closer than you think. There are the standard sunglasses and then you have actually rated sunglasses for various purposes. The more extreme the environment, the more the former gives a false sense of safety that just isn't there.
> the primaries are defined by the display, not by ambient illumination
In itself that is correct, but as you've noted, our own vision system isn't operating like that. The same display brightness and colors will be perceived very differently depending on the ambient light's brightness and color, and can also mean a severe breakdown in the dynamic range that can be made visible via a display.
And this ambient light also clearly impacts how prints are seen.
The problem is that it permeates writing in so many places. For example, games get more and more littered with this sort of nonsense, too. And worse, it is often also used as a vehicle to convey all sorts of ideologies. Many people don't care about these ideologies, but they get annoyed fast if someone shouts them into their face like a zealot. Plus it feels just fake, completely artificial.
The other problem with it: To me, as an adult, it feels like whoever wrote this made the assumption I'm stupid. This sort of writing is ok, up to a certain degree, for kids. But for adults? A lot of anime are aimed at the younger generations. Anime written for adults are done very differently.
The Matrix is heavily influenced by manga / anime, which you see in quite a few scenes in how they are shot. But many of the explanations that are done are part of the development of Neo, so they never really feel out of place.
Cyberpunk 2077, which does have on the nose dialogue here and there as part of random NPCs spouting stuff. But by and large it tells a story not just through dialogues but also visually. And the visual aspect is so strong that some reviewers completely failed at reviewing the game, they were unable to grasp it. Which is a huge issue, because we are talking about adults here.
I haven't read the actual paper, but alone from the abstract many questions come up.
Personally, I doubt the any "near" to "mid" term population decline will have larger effects on the climate change we are seeing. It is just too slow. Meaning that we certainly get (much!) larger effects about climate change done with other stuff, no doubt about that.
However, using that as an inverse argument to foster population growth is a stupid idea, because more people means more resources needed for everything, starting with food and water, climate change resistant shelter, and all the other stuff that is needed for actual living. All of that isn't created out of thin air. Considering that there is increased pressure just to provide food and water already (climate change anyone?!), the lower the population in the long run is, the better. Also, food supply destroys a lot of our environment, alone the meat industry is a planet wide killer because of that.
If I add all this up, population decline is a good thing. And if I read something like "Meanwhile, a smaller population slows the non-rival innovation that powers improvements in long-run productivity and living standards" I start to question the sanity of the people writing something like that.
If I look at one of the photography books in my shelf, they are even talking about 18 stops and such for some film material, and how this doesn't translate to paper and all the things that can be done to render it visible in print and how things behave at both extreme ends (towards black and white). Read: Tone-mapping (i.e. trimming down a high DR image to a lower DR output media) is really old.
The good thing about digital is that it can deal with color at decent tonal resolutions (if we assume 16 bits, not the limited 14 bit or even less) and in environments where film has technical limitations.
There is no system that fulfills your requirements.
It is even easy to explain why: Humans are part of all the moving pieces in such a system and they will always subvert it to their own agenda, no matter what rules you put into place. The more complex your rule set, the easier it is to break.
Look at games, can be a card game, a board game, some computer game. There is a fixed set of rules, and still humans try to cheat. We are not even talking adults here, you see this with kids already. Now with games there is either other players calling that out or you have a computer not allowing to cheat (maybe). Now imagine everyone could call someone else a cheater and stop them from doing something. This in itself is going to be misused. Humans will subvert systems.
So the only working system will be one with a non-human incorruptible game master, so to speak. Not going to happen.
With that out of the way, we certainly can ask the question: What is the next best thing to that? I have no answer to that, though.
Doesn't need video anymore, high end cameras can run wild on taking picture after picture and start doing so before you even fully pressed the shutter, to account for human delays and the ones of the tech itself.
I mean we are talking about a part of photography where even back in the days of film a camera would run through a roll of film in seconds for exactly this sort of thing.
If I see something like "At least on Linux, long and long long are both 64 bits in size." my skin starts to crawl. Not only that, but GCC defines __builtin_popcount() with unsigned int / long / long long, respective, i.e. even in the text it should be mentioned correctly (unless a different compiler uses signed types there ... ugh). The call is done with unsigned, using uint64_t as a type-cast, but using a fixed __builtin_popcountl() which translates to unsigned long. There are systems where this will fail, i.e. the only safe bet to use here is __builtin_popcountll() as this will cover at least 64 bit wide arguments.
Also, if a * b overflows within the result type, it is an undefined behavior according to the C standard, so this overflow check is at least not properly portable, either, and the shown code for that is actually buggy because the last A1 has to be A0.
These large corpos are so greedy to the point they harm themselves. I remember something similar with Amazon, where the Amazon shop had to redo the whole architecture from some microservice setup back to a monolithic approach because they used AWS and paid these weirdly structured prices like everyone else. Which made running a monolithic architecture under such constraints inherently cheaper. Not sure what the resulting compounded business cost for this "endeavor" was, but more often that not such things are never accounted for, so they don't show up as an issue.