jmb99
Joined 2 years ago
Joined 2 years ago
Note as well that I said heat density - different benchmarks (or applications) will load the CPU differently, and the same amount of power consumption will result in very different heat outputs (heavy single core use will result in part of the die and heat spreader getting really hot, whereas heavy multi core use will result in the whole die and heatspreader getting kinda hot). If the heatsink has a very high surface area and high airflow it might have the ability to dissipate quite a lot of heat, but if the contact surface sucks (or is aluminum) it might not actually be able to transfer heat away very effectively without a massive temperature delta - resulting in high CPU temps for single core use even with a high cooling capacity for multi core use, for example.
Your average person can’t understand all of these variables, and the average reviewer can’t control for all of them. So, “this CPU with these benchmarks in this case with this fan configuration” is the best you can really expect. Because otherwise, what reporting are you actually going to do? “This cooler with 3.2CFM of 26C airflow on a CPU dissipating 80W on one core and 10W on the other 7 cores results in a peak core temperature of 87°C and a package temperature of 81°C” is not useful reporting. Especially because, when the average person doesn’t understand it, they’re gonna buy a case fan that says 3.2CFM on the box and then wonder why their CPU’s throttling.
In… the downloads folder? How much more obvious does the location need to be?
Now if the right kernel exploit and a secure boot exploit are chained together then it’s possible. But at the point, you’re gonna be hosed no matter what you do.
Pretty useless if you use Microsoft’s keys. But with your own, depending on the attack surfaces you care about, can be pretty helpful
If the solution to smooth passkey use is “spend money” why the hell is anyone going to use passkeys over just using passwords for free?
Lack of pass-through could probably be argued the same way, although it is a bit more surprising.
If/when devices start shipping with cellular modems and eSIMs... honestly not sure. Faraday cage? Physically remove the modem? (If that doesn't prevent the device from booting.)
Admittedly I haven't confirmed that this results in no API calls in the latest few macOS releases but it definitely used to stop them, at least a few years ago.
If you only need ~50TB it’s probably both cheaper and easier to just buy hard drives, even today, factoring in the cost of the tape drive. Maybe even 100TB. I’m personally backing up ~225TB off-site these days and I still find AWS S3 glacier deep archive to be cheap enough - at current prices I’ve decided the hassle of doing tape again isn’t worth my time unless I’m over 300TB.
I don’t really see any drawbacks with storing them on the device, they should already be quasi-public knowledge (from warrants/etc) so it’s not like there’s a privacy/security risk there
There are exceptions to the above, like GamersNexus, who do take a slightly more scientific approach to things, but at the end of the day, most people don't care.