4 ms·
This is worth knowing about, but it is really a distant edge case. Calling it a peril of M1 ownership is a bit dramatic when you consider how few people it will
by blunte 5y ago
This is worth knowing about, but it is really a distant edge case. Calling it a peril of M1 ownership is a bit dramatic when you consider how few people it will affect.
- gjsman-1000 5y agoThis blog is well known for both deep original knowledge, and extreme hyperbole. There was a post about MacOS update size that compared the size of the updates to beating the backs of Mac users raw and ignoring their pleas.
- blunte 5y agoOk then. Literary license :)
- addicted 5y agoI am not sure which specific article you’re talking about, but MacOS update sizes were a massive issue. The real problem wasn’t the update size itself. The real problem was the updating through the Mac store, which would invariably fail to properly download the update if you were on anything outside a several hundred mbps connection, and even if you did successfully download it, would potentially fail to install and/or give really poor progress updates where it looked like it hadn’t installed. All the while eating up many gigabytes of space for I don’t know what.
- philistine 5y agoThe problem is still persistent now, I wouldn't talk in the past tense. Update sizes are positively ginormous.
- jfarmer 5y agoI think the title was meant to be wordplay: the perils of the M1 "Ownership System" and the perils of owning an M1 Mac.
- sylens 5y agoIsn’t there a chance this could show up in Macs provisioned by enterprise IT before being assigned to employees who sign in with their own Apple ID?