Imagine you're a function whose implementation body is written over time by you (the conscience). Your function is invoked once at your birth and seizes to execute when you die.
* You don't control what arguments are passed to your function
* But you do have complete control over the implementation
It's OK to verify your arguments, but then, once you realized you've been given less-than-ideal values, you don't have to continue processing them. Stop writing code that depends on these inputs and write your own implementation as if those arguments never existed. You're not the product of your input values, they're just there and it's your decision whether to use them or not.
Also, how are you dead weight if you're a millionaire? This would mean your parents are carrying you. Buy a house and GTFO then. Visit your parents once in a while. Call your mom.
I'm a bit confused. If you're trying to say that Huawei's P9 (released in 2016) took better pictures than Huawei's 6P (released in 2015) and than the iPhones, then I don't think there's anything to disagree over. They both took better pictures than the iPhones, seeing as they're both Huawei phones released shortly one after the other.
Now that I think about it, you might be saying that P9 was more wide-spread in the US than the 6P, which would also be confusing, because I don't think the P9 was officially sold in the US.
I had expected 8 slower cores to outperform the 2 slightly faster cores in multi-core benchmarks, so the results are somewhat surprising, but I guess Apple's wide pipeline design keeps on giving. Thanks for the benchmark data.
For what it's worth, the statement you quoted did not initially contain the number of cores. 6P felt super snappy (at least on Android 6, not so much on Oreo) and I added the cores for dramatic effect, but that backfired. I'll leave it as-is so others can notice and learn from my mistake once they read your reply.
The best 'cheap' phone that was ever released in the US was the $499 Google Nexus 6P by Huawei in 2015. It was an octa-core phone that made Apple's dual core iPhone 6s (also released in 2015) look like an overpriced joke. The 6P's aluminum body was lighter and thinner than the iPhone 6s, its camera took much better pictures _by far_ especially in low light conditions (restaurants, evening travel, etc), the iPhone's old backlit IPS LCD screen had _nothing_ on 6P's gorgeous AMOLED. It took Apple 2 years to catch up to the 6P, with their iPhone X, and even then it didn't beat the 6P in every category. It was a beast of a phone. Mine finally died last year after 2 years of heavy use and 4 years of being a backup phone.
Ooo... spooooky pointers... ancient prophecies speak of the Earth splitting in half and swallowing everyone who's ever thought about allocating memory.
I've been to Bermuda and tried this water. It had an odd taste - a bit smokey or 'pan fried' (if you can imagine that). I've been told it's because of the lime-based purification process, plus it sitting in an underground tank for a while. Did anyone else notice the peculiar taste?
* You don't control what arguments are passed to your function
* But you do have complete control over the implementation
It's OK to verify your arguments, but then, once you realized you've been given less-than-ideal values, you don't have to continue processing them. Stop writing code that depends on these inputs and write your own implementation as if those arguments never existed. You're not the product of your input values, they're just there and it's your decision whether to use them or not.
Also, how are you dead weight if you're a millionaire? This would mean your parents are carrying you. Buy a house and GTFO then. Visit your parents once in a while. Call your mom.