Ask HN: Sierra macOS 4gb download without confirmation, is this acceptable?
This blew my cell data quota for the month. I wasn't possible that a skype call could have taken so much data, even a long one.
I didn't have time to investigate the cause I was just irritated, and assumed maybe OSX had installed a patch to El Capitan, which is annoying enough. While I'd prefer to be notified for each of these downloads, I know I'd opted in for this and I'd be warned this time to make sure I had it switched off.
Today, I figured I'd try Sierra, and of course, it was the full OS installer that had been downloaded on my cell, the date and time and size all matched.
I am sure the definition of "Update" could be twisted here, but holy expletives, this is a royal pain.
I wonder what HN thinks about this? Do we accept that a full OS update should be part of the standard opt in for "app store updates"?
Obviously for my case, it was a problem.
27 comments
[ 2.8 ms ] story [ 70.7 ms ] threadUsers shouldn't have to worry about unattended OS downloads like this one happening without their permission or awareness.
Or, you know, just use skype on your phone
The real question is, why did it only try to update and download Sierra then?
This is one of the reasons I don't leave any downloads to automatic.
During the Skype call I had shitty QOS too, and yes, the full download had completed by the time I'd finished the meeting, because the MacBook was closed immediately after.
I will turn off automatic download now, obviously, but I honestly believe that a OS upgrade isn't acceptable as a background download.
Simply because it's not an automatically applied update.
Yeah, I totally agree. You might not even want it
On reflection, I don't think I'm actually gaining that much (or anything at all) by letting them run automatically anyway. It's a false convenience.
A computer without a network bandwidth display is like a car without a speedometer. I wish all OSes had this, would cut down on people's mystery wifi complaints.
Part of the reason might be that software engineers at companies like Microsoft and Google have unlimited data as a perk with their employees' personal cell phones (even still on Verizon today when a regular Joe cannot even get unlimited data anymore).
After leaving BigCo, I never upgraded my phone again because of the perk.
As far as opt-in or opt-out; we seem to be in the always on era... where computers and devices always assume it's up
I suppose Windows isn't any different. Linux on the other hand is much more frugal in terms of individual upgrade download sizes because the actual OS is just the kernel while the rest of the software can be updated independently.
May be there is a reason behind this. I would love to know why.
As an aside, and if it doesn't already, DHCP should have some way of altering clients that they're on a metered connection.
https://developer.apple.com/library/content/qa/qa1779/_index...
"For devices running iOS 7.1 and later, the update package may include only the differences between the old and new versions of a changed file instead of the full file. This may significantly reduce the size of the update package in the case where only a small part of a large file changes"
(Not sure why it says "may")
The real problem, obviously, is that the OS itself does not know if it is tethered to a data-capped mobile connection or an unlimited fixed line. If operating systems (both on mobile and desktop computers) were built to handle the first case, the user would have an option to stop any background activity or app updates. Like a “data-capped mode” for the entire OS.
I frequently use my mobile (with limited data) to give Internet access to friends who come from abroad and therefore have no data roaming enabled. Of course, once these mobiles see they're on WiFi, they assume they can download app updates. With LTE, it's easy enough to burn through a lot of data in no time.
I think it's simply the fact I got directly impacted that I feel differently.
That said, it's still 50/50 for me, but full OS upgrade downloads are not a simple update, and I think they should be a different opt in class.
The main reason is because these are not auto applied like a regular update, and the payload is in a different realm altogether.
The 'all' update - has to be a part of this process - similar events are happening with Win10 - its not mandatory, but it's very passive aggressive forceful. Why? the next business milestone depends on being able to move the customers to the next OS. (and then the next).