Welcome to the MacNN Forums.

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

You are here: MacNN Forums > Hardware - Troubleshooting and Discussion > iPod, iPhone & iPad > [things we take for granted] How come new iOSes have no backward compatibility troubl

[things we take for granted] How come new iOSes have no backward compatibility troubl
Thread Tools
Addicted to MacNN
Join Date: Dec 1999
Location: Tampa, Florida
Status: Offline
Reply With Quote
Feb 16, 2011, 02:28 PM
 
Even the oldest, crappiest apps keep working, whereas in the OSX context, applications made in 2008 may or may not not run on Snow Leopard.
Insane backward compatibility testing of current code?
Inclusion of old libraries and kernel modules, leading to bloat?
iOS design inherently doesn't get compatibility problems?
UNIX jail? Chroot? Emulation? Sandboxing?
Accident? Steve's voodoo?
Is this gravy train gonna stop? Hit a wall?
     
Posting Junkie
Join Date: Jan 2006
Location: Seattle, Washington
Status: Offline
Reply With Quote
Feb 16, 2011, 02:35 PM
 
iOS hasn't been completely rewritten from the ground up since 2008 like OS X has. Apart from a few thousand new APIs, the iOS that ships today on a new iPhone is the same iOS that shipped on the first iPhone in 2007.
     
Addicted to MacNN
Join Date: Aug 2004
Location: FFM
Status: Offline
Reply With Quote
Feb 16, 2011, 06:47 PM
 
Private API use is not allowed.
     
Mac Elite
Join Date: Jan 2000
Location: Columbus, OH
Status: Offline
Reply With Quote
Feb 16, 2011, 08:48 PM
 
Given enough time, some apps will fail as APIs become deprecated. After a few major iOS updates, the developer will have to update their app otherwise the app will fail. iOS hasn't been around long enough for this to become a problem.
HyperNova Software, LLC
     
Professional Poster
Join Date: Jun 2001
Location: Northwest Ohio
Status: Offline
Reply With Quote
Feb 17, 2011, 02:48 PM
 
Originally Posted by TETENAL View Post
Private API use is not allowed.
This.

Even back in the old days of Classic Mac OS (and even in the days of the Apple II), the biggest reason that apps would break in new releases of the operating system was apps that did things that Apple explicitly told developers not to do. The problem was that Apple didn't even follow its own advice and even their own apps would trip up because of it.

That's not to say that all apps that follow all the rules won't ever have backwards-compatibility problems, but the percentage that do is much smaller.
     
Professional Poster
Join Date: Jun 2001
Location: Northwest Ohio
Status: Offline
Reply With Quote
Feb 17, 2011, 02:51 PM
 
Originally Posted by msuper69 View Post
Given enough time, some apps will fail as APIs become deprecated. After a few major iOS updates, the developer will have to update their app otherwise the app will fail. iOS hasn't been around long enough for this to become a problem.
Also, I imagine that Apple can remove old, never updated apps from the store once they become so old that they wouldn't run on current versions of the iOS and the percentage of older versions that can run the app drops to a minuscule number.
     
   
Thread Tools
Forum Links
Forum Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Top
Privacy Policy
All times are GMT -5. The time now is 10:39 AM.
All contents of these forums © 1995-2011 MacNN. All rights reserved.
Branding + Design: www.gesamtbild.com
vBulletin v.3.8.7 © 2000-2011, Jelsoft Enterprises Ltd., Content Relevant URLs by vBSEO 3.3.2