Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Could it be that you where offline for a year or so?
No, iTunes 64-Bit requires OS X 10.7.0 or newer. See screenshot.


(click to enlarge)
 

Attachments

  • arch2.png
    arch2.png
    121.7 KB · Views: 324
Paves the way for intel chips in iPhones

Hm. I would have thought the other way around, meaning paving the way for Apple ARM in the Mac. Mainly because Apple was touting "desktop-class" processing with their new 64-bit chip.
 
And yet still no word of 64 bit Android. We're so far ahead of them it's hysterical. :D If you want 64 bit desktop performance on your mobile there is only one player in town.

I'm sure it'll take google and its handset manufacturers a metaphoric 5 minutes to catch up.

this android versus apple thing is quickly becoming a mine is bigger than yours game.
 
Hey look devs! Single app binaries to support 32 and 64 bit versions! In other words, there's really no need to try and sell us 64-bit versions of apps we've already paid you for when all you've done is recompiled them. I'm sure that won't stop some houses trying though.
 
Depends...
The changes can be quite significant to the point where certain parts of the code simply won't compile (or compile then crash your machine because they make wrong assumptions.)

In my view the apps that will benefit the most from being 64-bit, generally won't compile if they use 32-bit code.

Only if the Developer cant Code. Every good code works flawless. If Not its fail by design
 
I'm reminded of all the "WHY ISN'T ITUNES 64-BIT YET???" threads here, yet no one could actually explain the benefits of it being 64-bit for the average user.

I guess you ignored the responses saying it would improve performance. Of course, part of the reason people wanted to see the app go 64 bit was because that would force it to go Cocoa at the same time. And sure enough, when it went 64 bit there was a noticeable improvement in performance.

But the real problem with iTunes was that it wasn't optimized for multiple cores/threads. Sadly, after all these years they inexplicably STILL haven't done that yet.
 
It almost seems better to make a 32 bit version and a 64 bit version. So at some point when you need to stop updating the 32 bit version, the people will iOS 6 will continue to have a running copy.

This might avoid the problems with apps that say "we're no longer supporting iOS X, so don't download and install the update". This is a problem if I have iOS X+1 on a different device...

Or am I missing something there...

Gary
 
Developers with apps that function on both iOS 6 and iOS 7 will be limited to 32-bit development for the time being, but Apple has plans to support a single app binary for both 32-bit and 64-bit apps in the next month.
So I guess iOS 7.0.1 will bring single binary support.

The revenge of the fat binaries... ;)
With Universal apps including retina iPad assets and now adding 64-bit support it's too bad Apple didn't increase the flash storage capacity. We've been stuck at 16GB base capacity for new models for 4 years. Whatever happened to Moore's Law?
 
And yet still no word of 64 bit Android. We're so far ahead of them it's hysterical. :D If you want 64 bit desktop performance on your mobile there is only one player in town.

You have absolutely no idea what you're talking about. This is irksome.

Not only is the A7 not anywhere near desktop performance, on the very same day Intel was showing 64 bit cpus for Android.

http://www.dailytech.com/IDF+2013+Intel+Distances+Itself+From+Windows+8+Microsoft/article33363.htm

Apple is, unfortunately, ahead of precisely no one.
 
Removed

Probably removed since no developer should submit an app unless they've testing it on actual iOS devices running the claimed OS versions supported. Thus they should not be submitting a 64-bit iOS app unless they've actually tested it on an iOS device that runs 64-bit code.

Since those devices do not exist (outside Apple, and maybe a few select seed developers who were part of the media event, etc.) until the 20th, the note was pre-mature.

My guess is that the note will pop back up on Friday just after the devices are actually available to developers (the ones waiting first in line).
 
iMovie or iPhoto and a few other Apple apps are probably ready for the hybrid versions in-house (they've got the new compiler!).

Any new apps that don't need or want to support the older OSes.

Gary

That's what I was thinking. If it's just a month to wait for the method that is preferred, developers are going to wait a month. I'm also guessing most developers want to support pre-5s devices because they will be the majority of devices for a couple of years at least.
 
I think at this point devs would be crazy to compile and submit existing apps as 64bit apps that are ios7 only. Doing so will just seriously piss off existing users not wanting to update to iOS7. That said it might make sense for new apps, I just can't imagine save a few games that there are many new apps so dependent of 64-bit that it'd be worth alienating the entire IOS user base.

Like many (not most obviously) ill be waiting for an iOS7 jailbreak before updating. As slick as iOS7 is, I can't imagine going back to typing without SwipeSelection.
 
Sorry, but both of you guys come off as just ignorant Apple fanboys.

And yet still no word of 64 bit Android. We're so far ahead of them it's hysterical. :D If you want 64 bit desktop performance on your mobile there is only one player in town.

Android, in a way, is already 64-bit ready. They just have to update the kernel. But Android is built on the Linux kernel and there already is a 64-bit Linux kernel.

The best part is yet to come...Once they do have (multiple implementations of) 64bit chips to use, mass confusion will ensue with programs running only on certain processors, etc.

The reality is Apple is about to prove beyond a shadow of a doubt why Android is fragmented and more effort for devs to program for. Imagine making 6 or 8 binaries for your program vs. 2 for iOS7.0 and possibly one for iOS7.1.

You really have no idea what you are talking about. Android apps run on top of the Dalvik JVM. Once the JVM is updated, then all apps will work. There are already multiple processors on Android. All you have to do is compile an app once and it will work. There are ARM, Intel, and other processors and they all run current Android apps.
 
  • Disagree
Reactions: spartan1967
Sorry, but both of you guys come off as just ignorant Apple fanboys.

Android, in a way, is already 64-bit ready. They just have to update the kernel. But Android is built on the Linux kernel and there already is a 64-bit Linux kernel.

You really have no idea what you are talking about. Android apps run on top of the Dalvik JVM. Once the JVM is updated, then all apps will work. There are already multiple processors on Android. All you have to do is compile an app once and it will work. There are ARM, Intel, and other processors and they all run current Android apps.

It's really not nice to remove their rose colored glasses with RDF protection without warning them...
 
Sorry, but both of you guys come off as just ignorant Apple fanboys.



Android, in a way, is already 64-bit ready. They just have to update the kernel. But Android is built on the Linux kernel and there already is a 64-bit Linux kernel.



You really have no idea what you are talking about. Android apps run on top of the Dalvik JVM. Once the JVM is updated, then all apps will work. There are already multiple processors on Android. All you have to do is compile an app once and it will work. There are ARM, Intel, and other processors and they all run current Android apps.

I love Apple products, especially Macs, but I agree---fanboys are often ignorant of Android and arrogant for Apple. The Nexus 4 (if purchased with stock Android straight from Google Play) is an outstanding phone.
 
Wouldn't a single app binary result in a bigger file, hence a bigger download???

Apple should implement their AppStore to give a user the choice (making the most suited the default), to download either the 32-bit or the 64-bit version of the app, similar to how they let a user choose their videos between SD or HD.

What do you think about it?
 
Does this also mean we won't be able to target back to iOS 5?
 
Last edited:
And yet still no word of 64 bit Android. We're so far ahead of them it's hysterical. :D If you want 64 bit desktop performance on your mobile there is only one player in town.

And the irony is that Android phones actually have 2 to 3 times more RAM than iPhone. As was mentioned by many, at this point there are probably more disadvantages than advantages for phone applications to go 64bit. Because they all will get fatter (require more RAM and make app loading slower) without any performance benefits for the vast majority of them.

Also, most Android apps are Java apps. They are agnostic as to the CPU architecture. Android will just need new version of Dalvik (virtual machine) and all those apps will run just fine. In a way, Android is in much better shape with regard to switching to 64bits than iOS is.
 
Android, in a way, is already 64-bit ready. They just have to update the kernel. But Android is built on the Linux kernel and there already is a 64-bit Linux kernel.

You really have no idea what you are talking about. Android apps run on top of the Dalvik JVM. Once the JVM is updated, then all apps will work. There are already multiple processors on Android. All you have to do is compile an app once and it will work. There are ARM, Intel, and other processors and they all run current Android apps.

Android is _at_this_minute_ just as 64-bit as iPhone has been the last 4 years since that's how long as OSX's xnu kernel been 64-bit clean. There's no shipping 64-bit hardware running Android only prototypes. There's no production ready version of Android, nor Dalvik, just alphas and no ship dates. That's called vaporware in most books.

Yes, Google, Samsung, Intel and every other player just have to…
Guess what. Apple just did.
 
Depends...
The changes can be quite significant to the point where certain parts of the code simply won't compile (or compile then crash your machine because they make wrong assumptions.)

In my view the apps that will benefit the most from being 64-bit, generally won't compile if they use 32-bit code.

Yes, it all depends.

Existing 32-bit code will usually compile to 64-bit, but just compiling doesn't mean the code actually takes advantage of any of the benefits of 64 bit. Most apps which are simply user interfaces clicking buttons and getting data from the internet to display on the screen will be no problem converting.

But complex high frames-per-second 3-d games with all sorts of algorithms for displaying the 3d worlds might make assumptions of 32-bit data which would fail at 64-bit.
 
In a way, Android is in much better shape with regard to switching to 64bits than iOS is.
Yeah? Apple just switched, Android didn't. 32-bit iOS apps will continue to work as great as they've ever done with no need (zero) for recompilation of anything. One only need to if one want to use the special features where 64-bit or ARMv8 do shine. If your app doesn't, then you can just sit back and do absolutely nothing.

It's pretty rich to come and say that Android is in better shape when it's actually in no shape at all but vaporware.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.