11–20 of 103 posts
Rebooted several times. My iPhone 7s, and two older iPhones upgraded to 10.3, as well as another iPad. Why is the iPad Pro different?
Changing filesystem for billions of phones in a point release? That doesn't sound fun.
Changing filesystem for billions of phones in a point release? That doesn't sound fun.
Initially, I was thinking the same thing. Given how fast the average Apple consumer updates to major iOS releases, I imagine that rolling it out over a point release is actually part of the plan. Presumably, if something does go wrong on the individual level, the support burden on the genius bars will be lower (since major iOS releases have traditionally come alongside hardware releases), and if a major bug is found,…
If I were somehow in charge of it, I imagine I'd want to do it like: 1) ship it as officially supported on the Mac, but off by default. 2) a year or two later, ship it as officially supported on the Mac, on by default, but still allow HFS+ as an option. 3) A year or two after that, if all has gone well, then introduce it into iOS (where presumably it's not reasonable to make it optional).
It's really weird to me that Apple is rolling it out to hundreds of millions of devices all at once, when it's not even a bootable filesystem on any of their platforms yet. Seems like the kind of thing where you'd want to take a more gradual approach.
I get that HFS+ is super old and I see why Apple wants to switch to APFS. But I don't get why they're in such a hurry.
Here's hoping their approach works well, in any case!
Earlier quoted context omitted.
Yeah this is kind of causing a full on panic in the office today. If Apple fucks something up, and your app don't run no more, it's your fault and it's now your problem .
You literally can't leave a review saying "This version of iOS is shitty and it breaks all my apps." But you can absolutely throw a brick through my front window.
Changing filesystem for billions of phones in a point release? That doesn't sound fun.
Initially, I was thinking the same thing. Given how fast the average Apple consumer updates to major iOS releases, I imagine that rolling it out over a point release is actually part of the plan. Presumably, if something does go wrong on the individual level, the support burden on the genius bars will be lower (since major iOS releases have traditionally come alongside hardware releases), and if a major bug is found,…
Wouldn't this be valid semver if the APIs or general functionality hasn't changed? Or isn't expected to?
I think this doesn't address the real problem though, which is that ratings reset after every app update. This means that app developers have to constantly ask for reviews, which is exhausting as a user.
Earlier quoted context omitted.
You literally can't leave a review saying "This version of iOS is shitty and it breaks all my apps." But you can absolutely throw a brick through my front window.
Actually with 10.3 you can: https://9to5mac.com/2017/01/24/apple-will-let-developers-rep...
Earlier quoted context omitted.
Initially, I was thinking the same thing. Given how fast the average Apple consumer updates to major iOS releases, I imagine that rolling it out over a point release is actually part of the plan. Presumably, if something does go wrong on the individual level, the support burden on the genius bars will be lower (since major iOS releases have traditionally come alongside hardware releases), and if a major bug is found,…
Rolling it out first on iOS at all doesn't seem like the right approach. If I were somehow in charge of it, I imagine I'd want to do it like: 1) ship it as officially supported on the Mac, but off by default. 2) a year or two later, ship it as officially supported on the Mac, on by default, but still allow HFS+ as an option. 3) A year or two after that, if all has gone well, then introduce it into iOS (where presumab…
I'm excited about exposing to app developers a way to ask for ratings. Specifically, the ability to opt out of them. I think this doesn't address the real problem though, which is that ratings reset after every app update. This means that app developers have to constantly ask for reviews, which is exhausting as a user.
What's the reasoning behind this? On Android, reviews for prior versions have a "This review was left for a previous version." banner at the top of them, but the star aggregates are all still there. How do apps keep reviews if they're wiped out every time an app updates?
Changing filesystem for billions of phones in a point release? That doesn't sound fun.
Yeah this is kind of causing a full on panic in the office today. If Apple fucks something up, and your app don't run no more, it's your fault and it's now your problem .