3 ms·
I'm curious how this plays out in the long term. Apple seems very aggressive about blocking 3rd party code from running on their hardware. I think the goal of
by burtonator 8y ago
I'm curious how this plays out in the long term.
Apple seems very aggressive about blocking 3rd party code from running on their hardware.
I think the goal of the T2 is to block Hackintosh and also to block hardware upgrades.
At some point Apple is going to lock this down. They have a history of doing so and giving them the benefit of the doubt is probably a bad call.
- angott 8y ago> I think the goal of the T2 is to block Hackintosh and also to block hardware upgrades. Although there's no way for us to really know, I don't really think that's their priority. Sounds more like a side-effect. Consumers capable of assembling, installing and updating a Hackintosh are probably less than 0.1% of the entire Apple user-base. They are peanuts, from a merely commercial point of view. They also don't really need to prevent hardware upgrades with an enforcing chip. They are already preventing hardware upgrades by releasing hardware that physically cannot be upgraded. Just think about their laptops released in the last 5 years, with RAM blocks and SSDs soldered to the motherboard...
- _fzslm 8y agoAdding to this - Apple manufactures new products with both upgradable hardware and T2 chips (well, product - the Mac Mini with the T2 chip and upgradable memory), and the long-awaited Mac Pro refresh will be an upgradable computer and presumably will have a Tx chip.
- jki275 8y agoI don't think that's the goal of T2 any more than the goal of the TPM is to block alternate OS or hardware upgrades. Apple lays out pretty well what the T2 chip does in their documentation.