iOS 11

Second beta this week, beta 9/ public 8.

A glitch in the iPad dock is fixed. Haven’t noticed anything else. Hoping what I think is a bug, namely, connecting AirPods, is gone, but haven’t tested it yet.
 
  • Like
Reactions: longisland94
I updated my phone yesterday. I've never seen a conclusive "what's fixed" list anywhere, plus the last 2-3 updates have only been 40-60mb in size. I was curious if Apple "patches" binaries since these updates are so small.
 
More ARkit demos. This could be the most awesome feature of iOS 11.
 
I updated my phone yesterday. I've never seen a conclusive "what's fixed" list anywhere, plus the last 2-3 updates have only been 40-60mb in size. I was curious if Apple "patches" binaries since these updates are so small.
WIth heavy use of libraries and SDKs, I would imagine that the programs themselves aren't all that large and they're replacing them rather than patching them. That said, Windows 98se was only about 35MB all-in.
 
I updated my phone yesterday. I've never seen a conclusive "what's fixed" list anywhere, plus the last 2-3 updates have only been 40-60mb in size. I was curious if Apple "patches" binaries since these updates are so small.


There are release notes. A lot of it is really minor fixes, some of which also involve third party apps.
 
Don't have iOS11 and probably will not upgrade. I'm getting warnings from app developers that iOS 11 will not support their app. They will notify me when they are ready.

Scott- I recall you had a Q-See security camera DVR. Have you received a notice it doesn't support iOS11? I do use the mobile app to access the DVR for playback when traveling. The other apps I have are medical records and my cardiologist notifications. There are several others I have that are not critical as the two I mentioned.

In the meantime, I guess the best thing for me to do is shut off auto updates.
 
BTW, go to Settings, General, About, Applications to see a list of Apps that won't be supported by IOS 11. I have 11 but don't care about most of them.
 
If that's the case, developers have had plenty of time to work on that too.

I think in some cases the original developers have moved on to other things. I'm not familiar with these apps but back in my old COBOL days changing an application from 16 to 32 bit was usually just a recompile.

I do have a couple apps I need to find a replacement for.
 
I'm not familiar with these apps but back in my old COBOL days changing an application from 16 to 32 bit was usually just a recompile.
I'm guessing with today's compilers, anything that's incompatible between 32 and 64 bit will be flagged and they'll know what needs changing. Not saying it's automatically easy to update though but they know what to work on.

From what I can see, since 2013, when Apple switched to a 64-bit processor, that should have been a pretty good clue to developers. Then, as of Feb 2015, Apple stopped accepting 32-bit applications into the App Store ! 4 months later, you couldn't even add updates to existing apps if they were still 32-bit.

I think you're right - the developers have moved on. No updates in 2+ years is a telling sign.
 
This is actually turning out to be a good excuse to clean house of old unused apps. I have run across a couple that there are newer versions of the app available to buy (of course). Another old app for reading QR codes won't be needed as the photo app in IOS 11 does that.
 
I'm not familiar with these apps but back in my old COBOL days changing an application from 16 to 32 bit was usually just a recompile.
Unless the COBOL compiler (or any other development platform or framework) you were using was abandoned. This may be what has happened as Apple left earlier development platforms in the dust in favor of Swift.

Sure, it was a long time ago and they should have kept up (assuming there was a large enough market for their app), but porting isn't always a matter of "recompiling".

COBOL, in particular, typically isn't compiled into native executables; it is frequently "translated" to p-code so that it may run on any processor that has the necessary runtime interpreter.
 
At work, going from 16-bits to 32-bits meant moving from the PDP-11 platform to the VAX-11 platform. The biggest difference there was not so much the BASIC, FORTRAN, or COBOL program, it was changing the Link options to go from Overlays to Virtual Memory. After that, you could eliminate a lot of the common areas you needed so you could swap program sections in and out of memory since the VMS operating system took care of the Virtual memory management. Same thing with moving to 64-bit code on Alpha (and Itanium) but there the Architectural differences were more significant going from a CISC CPU to a RISC CPU. Memory Page sizes changed, as did integer boundaries, being aligned to longwords instead of words or bytes.

I've got a number of 32 bit Apps on my iPhone, so I guess I need to clean house, too. Like Hall mentioned, updates have not been done for several years in some cases.
 

Users Who Are Viewing This Thread (Total: 0, Members: 0, Guests: 0)

Who Read This Thread (Total Members: 1)

Latest posts