Also, Apple now has a 3 year period before all phones offered for sale will all be 64-bit. OS7 is 64-bit on the 5S and I wonder when Android will be 64-bit? Samsung????
Apple makes these changes to set themselves up for something down the road. Nothing is by chance here. That goes for the finger print scanner...presented as a side note almost but where will it be in a year or 2. The operate on vision for the future not a flash today and gone tomorrow.
Likely, the next iPads will exploit the 64-bit A7 (A7X ?) hardware and iOS 7 in ways that the iPhone never will. I can envision a 12" iPad with a 256 GB SSD and 16 GB RAM.
AIR, somewhere around iOS 5, Apple exposed the ProRes Codecs/APIs -- then removed them after several weeks. With the A7X, OpenGL, OpenCL, an iPad could do some serious audio, video, gaming work.
Then there is that easily overlooked iOS device -- the AppleTV. Add the same specs to that little box and you have a great gaming console and delivery vehicle for 4K video.
Add Thunderbolt and the same package could be used as a stand-alone server, part of a server farm -- or as part of a video render farm. Apple already has software that parcels out work to multiple Macs to be processed in parallel... no big deal to convert that to 64-Bit iOS 7.
64-bit CPU/GPU + 64-bio iOS == "We're not in Kansas, anymore!"
Further, APK files support multiple architectures. The installer extracts the appropriate binaries for the platform at install-time. APKs are limited to 50 MB, so if you have a lot of native code for a lot of architectures, you'd need the multiple APK support.
Still this is not fat binary support, it only a fat installer trick for managing multiple single arch binary
I dont understand this move by Samsung, they just released the new Note and 10" Tablet last week, and today they say.. but we will have 64 bit version next year. What is there supposed to tell consumers interested in buying a Samsung Note and 10" Tablet?
Was this a wise business move or did they just shoot themselves in the foot by telling consumers to wait for the next update?
Interesting... With all the hype about the iPhone announcement, I forgot about the recent Sammy releases.
Seems that Sammy is also stealing ideas from the late Adam Osborne... pity.
64 bit will help out the gamers on an iPhone, but the reason it is critically important and will make a difference is because it will boost the performance of iPads. Almost certain the iPads will be getting a CPU upgrade in the next month or so. For Apple shareholders, this will be important. The tablet market in the long run is the holy grail. The tablet market will expand more slowly and for a much longer period of time and whoever wins the tablet market will own the computer market. In the long term, Microsoft is in serious trouble because they don't have a mobile platform.
This needs to be repeated until it sinks into some thick heads. Apple is in this for the long haul and is working towards computing for a decade into the future. I think the iPhone only exists because they saw it as a good way to transitin people into the iPad. And having sold a few they realized that future computing would come in three favors: mobile (tablets) very mobile (phones) and that stuff that grandma used to do, you know with the big screen? That stuff companies do now? Not mobile? What is it called? Oh yeah, desktops...
The 64 bit combined with the performance upgrade is going to make a huge difference in tablets. And Apple controls it. The hardware, the cores, the software, all of it. And very soon at the rate they are improving chips your iPad will be running very very close to your desktop in speed.
How hot does this chip run? Anyone know? Can they give the iPad a dual chip? Four cores? Eight? How far away is that? And when your iPad has 128 gigs and desktop speed and can reach the cloud from almost anywhere, why would you buy a computer?
Already in my house we are getting closer to this every day. We have a desktop that is essentially a server or big iron. Yes, I have to rip the occasional movie, and I still keep iPhone and iPad backups there, but except for 2-3 times a week doing short intensive tasks, it could be stored in a closet and still do its job. But we have 4 iPhones, 3 iPads, and an iPod that get used on a near constant basis.
Which market do you want to control, the past, or the future.
Skate to where the puck will be...
Yeah! Yeah! Yeah!
and that little puck looks a lot like an AppleTV package.
From a technical standpoint, 64 bits is not needed for a mobile device. This change is all about bragging rights.
Hopefully consumers will wise up to the lack of need for 64-bits and save themselves some money.
1) If it wasn't needed, I don't think the most profitable tech company in the world would undertake this massive change and implement it.
2) Consumers don't pay more for this 64-bit iPhone. That, and the other improvements, are all free of charge. Just think of the price difference in cropped CCD vs Full Frame camera sensors. Now think of the *slightly* bigger sensor Apple put in their phone...without charging more. We should thank them. 64 times over.
Did you make the same comment when Apple copied the larger screens on typical Android devices for the iPhone 5?
I think he means that Samsung is quick to respond that they too will have 64 bit phones. Real pity though the journalist didn't ask them when they decided to do so, and when they started the project. I guess, like their sales numbers, with Samsung you'll just never know.
Come on dude, the get out of the Samsung's mith.............they are just fooling people. As of now Apple has not copied any one at least Samsung and they won't ever. However, there are some new age customer who love to have large screen for their video playback and for them Apple is already working and they will provide as the best display which will be best for the consumer.
Also, have you seen how hard to keep those big screen phone while working or traveling etc. Also, remember one thing Apple won't do anything silly "Just to show off", if they feel that it would be beneficial for their customer they will sure update the screen and other hard ware.
Why fat binary (as opposed to multiple single arch binaries) is important?
There is many advantages of having a single binary for multiple architecture.
On the developer sides, it greatly simplify project development by managing all plateform with the same codes and distributing as one apps for all device. Imagine the update hell for developer who needs to keeps track of every specific built.
On the users side, It render the transition to a new architecture invisible to them. Having the same apps that could run on legacy and new architecture without needs for user to update or install a separated version of the Apps.
Without Fat binary Apple would be unable to make the Intel and 64 bit transition. Just look at Windows SysWOW64 ugliness, where user has to choose between multiple drivers and apps version depending if they use an 64bit Windows or not.
Still this is not fat binary support, it only a fat installer trick for managing multiple single arch binary
A "fat installer" automatically selects the appropriate build to install. A fat binary includes builds for all architectures including ones that you don't need, and your device decides at runtime which binary to use. Both approaches let the developer target multiple platforms.
A "fat installer" automatically selects the appropriate build to install. A fat binary includes builds for all architectures including ones that you don't need, and your device decides at runtime which binary to use. Both approaches let the developer target multiple platforms.
One thing I don't know about the Android APK stuff, does every build shares the assets, like gui stuff or they are duplicated for every build included in the APK? Because on OSX, the UI part and assets are store outside of the binary and being share between all architecture include within the binary. So adding more target arch to a fat binary on OSX doesn't add much to the size of the apps.
One thing I don't know about the Android APK stuff, does every build shares the assets, like gui stuff or they are duplicated for every build included in the APK? Because on OSX, the UI part and assets are store outside of the binary and being share between all architecture include within the binary. So adding more target arch to a fat binary on OSX doesn't add much to the size of the apps.
APK is a zip file. It contains the binary (executable, library) file(s) as well as asset files.
Second, 64 bit is part of a roadmap for the future, with almost no benefit today. This is true for both Samsung and Apple, but Samsung has reached the critical limit before Apple. That's because their current phones ship with 3GB RAM, almost the 4GB limit. iPhone 5s ships with only 2GB RAM (iPhone 5 has 1GB). Read this: http://news.cnet.com/8301-1035_3-57602372-94/the-real-reasons-apples-64-bit-a7-chip-makes-sense/
Points to Note.. Samsung's like a labror manufacturing stuff as per Apple design. There is no Samsung R&D involved in this except there machinery involved in fabrication.
Samsung device benchmarks cant be trusted coz they have a program , that overclocks there CPU's only before certain benchmark software's run. They don't operate there device full time at that clock speed. If they did it would kill there battery.
And your wrong about 64 bit not benifiting apple.
Games like Infinity blade 3 already are 64 bit apps, that use the power of 64 bit computing. Do your research and don't bluntly post links around !
Comments
Likely, the next iPads will exploit the 64-bit A7 (A7X ?) hardware and iOS 7 in ways that the iPhone never will. I can envision a 12" iPad with a 256 GB SSD and 16 GB RAM.
AIR, somewhere around iOS 5, Apple exposed the ProRes Codecs/APIs -- then removed them after several weeks. With the A7X, OpenGL, OpenCL, an iPad could do some serious audio, video, gaming work.
Then there is that easily overlooked iOS device -- the AppleTV. Add the same specs to that little box and you have a great gaming console and delivery vehicle for 4K video.
Add Thunderbolt and the same package could be used as a stand-alone server, part of a server farm -- or as part of a video render farm. Apple already has software that parcels out work to multiple Macs to be processed in parallel... no big deal to convert that to 64-Bit iOS 7.
64-bit CPU/GPU + 64-bio iOS == "We're not in Kansas, anymore!"
Further, APK files support multiple architectures. The installer extracts the appropriate binaries for the platform at install-time. APKs are limited to 50 MB, so if you have a lot of native code for a lot of architectures, you'd need the multiple APK support.
Still this is not fat binary support, it only a fat installer trick for managing multiple single arch binary
I don't know why they don't buy Blackberry. I'm no expert, but from what I've heard it's a modern OS built on a unique Unix kernel.
At least it would give them something to build on that makes more sense than a rip-off of Java bolted onto a rip-off of Unix.
Interesting, I had never though of that before. That does potentially make sense.
No, Apple invented the Trinary Number System -- and the Trinary Digit.
Why fat binary (as opposed to multiple single arch binaries) is important?
Interesting... With all the hype about the iPhone announcement, I forgot about the recent Sammy releases.
Seems that Sammy is also stealing ideas from the late Adam Osborne... pity.
Still this is not fat binary support, it only a fat installer trick for managing multiple single arch binary
You're arguing about semantics, so I'm done.
Yeah! Yeah! Yeah!
and that little puck looks a lot like an AppleTV package.
Samsung still on Windows hey? Really, they have no taste.
1) If it wasn't needed, I don't think the most profitable tech company in the world would undertake this massive change and implement it.
2) Consumers don't pay more for this 64-bit iPhone. That, and the other improvements, are all free of charge. Just think of the price difference in cropped CCD vs Full Frame camera sensors. Now think of the *slightly* bigger sensor Apple put in their phone...without charging more. We should thank them. 64 times over.
I think he means that Samsung is quick to respond that they too will have 64 bit phones. Real pity though the journalist didn't ask them when they decided to do so, and when they started the project. I guess, like their sales numbers, with Samsung you'll just never know.
Come on dude, the get out of the Samsung's mith.............they are just fooling people. As of now Apple has not copied any one at least Samsung and they won't ever. However, there are some new age customer who love to have large screen for their video playback and for them Apple is already working and they will provide as the best display which will be best for the consumer.
Also, have you seen how hard to keep those big screen phone while working or traveling etc. Also, remember one thing Apple won't do anything silly "Just to show off", if they feel that it would be beneficial for their customer they will sure update the screen and other hard ware.
Why fat binary (as opposed to multiple single arch binaries) is important?
There is many advantages of having a single binary for multiple architecture.
On the developer sides, it greatly simplify project development by managing all plateform with the same codes and distributing as one apps for all device. Imagine the update hell for developer who needs to keeps track of every specific built.
On the users side, It render the transition to a new architecture invisible to them. Having the same apps that could run on legacy and new architecture without needs for user to update or install a separated version of the Apps.
Without Fat binary Apple would be unable to make the Intel and 64 bit transition. Just look at Windows SysWOW64 ugliness, where user has to choose between multiple drivers and apps version depending if they use an 64bit Windows or not.
Still this is not fat binary support, it only a fat installer trick for managing multiple single arch binary
A "fat installer" automatically selects the appropriate build to install. A fat binary includes builds for all architectures including ones that you don't need, and your device decides at runtime which binary to use. Both approaches let the developer target multiple platforms.
Interesting, I had never though of that before. That does potentially make sense.
I thought Blackberry is now based on QNX (RTOS).
A "fat installer" automatically selects the appropriate build to install. A fat binary includes builds for all architectures including ones that you don't need, and your device decides at runtime which binary to use. Both approaches let the developer target multiple platforms.
One thing I don't know about the Android APK stuff, does every build shares the assets, like gui stuff or they are duplicated for every build included in the APK? Because on OSX, the UI part and assets are store outside of the binary and being share between all architecture include within the binary. So adding more target arch to a fat binary on OSX doesn't add much to the size of the apps.
APK is a zip file. It contains the binary (executable, library) file(s) as well as asset files.
APK is a zip file. It contains the binary (executable, library) file(s) as well as asset files.
Do you know if the GUI is part of the binary on Android apps?
The layout files, images, strings, etc are separated from the binaries.
I taped 2 samsung phones together and have 64 bit processing. Thanks samsung. I want to be in the commercial next.
A couple of things...
First, don't bash Samsung for making junk. Why? The A7 is made by Samung, at least in part if not entirely: http://************/2013/07/31/apples-upcoming-a7-iphone-chip-will-have-samsung-components-code-inside-ios-7-reveals/
Second, 64 bit is part of a roadmap for the future, with almost no benefit today. This is true for both Samsung and Apple, but Samsung has reached the critical limit before Apple. That's because their current phones ship with 3GB RAM, almost the 4GB limit. iPhone 5s ships with only 2GB RAM (iPhone 5 has 1GB). Read this: http://news.cnet.com/8301-1035_3-57602372-94/the-real-reasons-apples-64-bit-a7-chip-makes-sense/
Third, benchmarks show that A7 is twice as fast as A6, which puts it around the same performance as today's Galaxy S4: http://www.primatelabs.com/blog/2013/03/samsung-galaxy-s-4-benchmarks/
Points to Note.. Samsung's like a labror manufacturing stuff as per Apple design. There is no Samsung R&D involved in this except there machinery involved in fabrication.
Samsung device benchmarks cant be trusted coz they have a program , that overclocks there CPU's only before certain benchmark software's run. They don't operate there device full time at that clock speed. If they did it would kill there battery.
And your wrong about 64 bit not benifiting apple.
Games like Infinity blade 3 already are 64 bit apps, that use the power of 64 bit computing. Do your research and don't bluntly post links around !