Anything the cache doesn’t have, causes a cache miss, which passes it through.
So when you request the large file, the CDN (cache) doesn’t have it, so it immediately passes through to the original source. The details of how this is implemented don’t really matter in the sense that they are not going to host the large file(s) in the CDN, so they will always fall through.
Apple is in FAANG. For some reason (likely related to 2015-17 era SWE compensation) FANG just includes Netflix (with amazon facebook and google) and not Apple.
They did not try to lower the gear on their first landing. It would have lowered. They raised the gear. It was in the commanded gear up (stowed position) when they landed and the indicator would have shown it was up.
Bitcoin is a pretty reasonable story for how this occurs - first you start on CPU, then GPU, then custom ASICs.
If the financial motivation is there, companies will build custom hardware. Companies like Apple and Google (TPUs) are building custom processors for various purposes.
Sometimes losing that information is very useful however, to arrive at a representation that has a specific meaning.
For example, an x-ray computed tomography (CT) image volume in 3D may be projected into various 2D synthetic planar x-ray projections (digitally reconstructed radiographs).
There are countless situations where projections are very useful.
Apple’s announcing their desktop ARM strategy next week.
Given how many iOS and Mac devices (many Macs have an ARM processor for things like the touchbar) Apple ships, they’re already one of the larger custom high-end ARM licensees. It will be interesting to see how it goes for them.