Live data from Hacker News

Apple releases iOS 10.3

9to5mac.com

71–80 of 103 posts

Re: Apple releases iOS 10.3

#71
post #8

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,…

> It stills feels wrong on a gut level, and semver folks might not be happy with it, but it seems to make some real sense. Wouldn't this be valid semver if the APIs or general functionality hasn't changed? Or isn't expected to?

I'm far from an expert on file systems or semantic versioning, but the one thing I've heard is that APFS changes the way filenames are written to and read from disk. HFS+ (the old file system Apple OSes used) would automatically normalize file names so you couldn't have two files with names that look the same to a user but are represented with different byte sequences. APFS does not do this on the file-system level. (I heard thirdhand that some APIs might still do the normalization, but I don't have any links or details on that and don't want to spread bad info.)

http://mjtsai.com/blog/2017/03/24/apfss-bag-of-bytes-filenam...

Re: Apple releases iOS 10.3

#72
post #70
post #62

Earlier quoted context omitted.

I've noticed a perceived decreased in IO latency, but haven't scientifically measured it.

The whole OS seems more snappy to me. Wonder if they have somehow figured out how to file access latency? Perhaps less of the filesystem metadata needs to be accessed on each file access.

HFS+ has a global lock so only one process can access the file system at a time. I would imagine having APFS clear out that limitation speeds things up dramatically.

Re: Apple releases iOS 10.3

#73
post #54

Backup first. Both my parents phones went to recovery mode. They have an iphone 5c and another old model. Going to see if I can extract data. They didn't have itunes backups.

It's generally never a good idea to upgrade immediately to the new versions of iOS, as there are invariably problems.

Re: Apple releases iOS 10.3

#74

Just updated all my devices and I must admit that things feel snappier, even the 5.

How do you know it isn't the placebo effect? I once had one of my customers saying that a certain feature in my product was faster after an upgrade, but I hadn't actually touched that feature...

Re: Apple releases iOS 10.3

#75
post #13
post #8

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…

The problem with supporting APFS and HFS+ at the same time is that FileVault and Time Machine need to be very different on APFS.

FileVault can take advantage of the transparent encryption feature of APFS and TimeMachine can simply backup a snapshot of the file system.

I don't know if Apple (who likes to drop things) will support both concepts.

Also the reason why I assume that APFS will be coming to macOS in the next major release and not in a point release.

Re: Apple releases iOS 10.3

#76

Earlier quoted context omitted.

I have a device that I unregistered from the beta's and it never picked up a newer version, I had to manually restore it.

I had the same issue but a manual reinstall wasn't necessary. I believe the problem was that in the developer > profiles menu there is a certificate for beta updates that needs removed. Something along those lines.

That is correct. You have to unregister yourself and remove that beta profile.

Re: Apple releases iOS 10.3

#77

I've been running the beta for a few weeks now. The thing that stands out the most? They changed the filesystem, and I haven't noticed a thing - the upgrade time wasn't even significantly longer. If anything, the beta has been more stable than 10.2 releases. The fact they've pulled it off so seamlessly is pretty impressive. Heck, the majority of users won't have a clue that their filesystem has changed, and that's th…

    > I've been running the beta for a few weeks now. 
    > The thing that stands out the most? They changed 
    > the filesystem, and I haven't noticed a thing
On the other hand, maybe the file system only catastrophically fails every few months.

Re: Apple releases iOS 10.3

#78

I've been running the beta for a few weeks now. The thing that stands out the most? They changed the filesystem, and I haven't noticed a thing - the upgrade time wasn't even significantly longer. If anything, the beta has been more stable than 10.2 releases. The fact they've pulled it off so seamlessly is pretty impressive. Heck, the majority of users won't have a clue that their filesystem has changed, and that's th…

> I've been running the beta for a few weeks now. > The thing that stands out the most? They changed > the filesystem, and I haven't noticed a thing On the other hand, maybe the file system only catastrophically fails every few months.

That's textbook FUD. You could say that about anything.

Re: Apple releases iOS 10.3

#80
post #67
post #45

Earlier quoted context omitted.

3-5 years seems to be pretty typical for a filesystem to go from merely available to being battle tested enough to use without thinking about it. Bugs could destroy people's data (and the cloud won't necessarily help if the bugs corrupt data rather than erase it). What's the hurry?

> Bugs could destroy people's data (and the cloud won't necessarily help if the bugs corrupt data rather than erase it). There's no reason to expect bugs if you have a comprehensive test suite and extensive internal and beta testing (like with a million of registered iOS developers running it for months). Doubly so if you control most of the APIs and interactions with the OS tightly in your platform (as iOS does).

Which is why the rest of iOS has no bugs?

This statement makes me wonder, have you written any software before?

Post reply on HN