lxmcneill

Would either of you please be so kind as to cite your sources?

Huh, was totally unaware of this. For me this has good implications for ingesting CSVs/.xlsx to dicts. Clean-ups / type hinting is required at times for dirtier documents.

In theory, yes. Since driving one 60hz 4k display at 4:4:4 chroma takes roughly 18gbps then daisy chaining 2 displays should be possible.

"Users will only store phone numbers in your product's phone number fields"

Not entirely sure what this point is trying to achieve. Do you read a birthday field expecting a phone number 99% of the time? Should you read a phone number field expecting an email address? And at what point in that process did you decide that not having data validation on both ends was a good idea?

I think this has less to do with respect and more to do with detracting from the original discussion e.g. source code integrity having nothing to do with human genitalia.

Jeff covered this in the post (GameDays, excessive amounts of auditing, etc.). Regarding the resource limits you suggest, they mention metrics of 50+ pB of data movement and 3.34 trillion DynamoDB queries in 30 hours, all of which they elastically scale down after the event... so I'd say resource limitations are more in terms of humans on-deck and crisis management, rather than physical limitation of hardware.

(edited to correct size - was 52 pB not 520 pB...)

The last time I went to pick up a product (AirPods) it required government issued photo ID (Australian driver's license), even though I had the Apple Store app which made the purchase installed on my phone.

I think they got their aspect ratio statement backwards. Surely 16:9 (iPhone 7) content appears pillarboxed on the 19.5:9 screen (iPhone X) and iPhone X content appears letterboxed on the iPhone 7?