Well, since ARM opened the gates, this was expected.
I just hope that these Exynos chips will have the LTE support needed in the US, eliminating the need for Qualcomm chips for US versions.
That being said, I would really be surprised if Qualcomm would not come out with their own 64 bit version.
ARM released 64-bit cores late last year already. Why is this a surprise?
It was originally released for low-power server racks running Linux...where they actually had more than 4GB of memory. Most phones won't go over that memory limit for a while since there's no real need to
so Android will support 64 bit instructions?? Not any time soon!
Not a big deal, all they need to do is recompile it with an ARM64 compiler and maybe swap in some optimized ARM64 libraries/algorithms.
For apps that follow Google's Android development guidelines, the rest of the code is Java so it does not really matter what the underlying OS or architecture is. Apps will use whatever instructions the Java runtime supports.
64-bit is overated. It took what...a decade on the PC and till today, most PC apps are still 32-bits except a handfuL of server apps or high-end productivity apps.
Slapping a 64-bit cpu into a phone is not going to make existing codes runs any faster or better. In fact,64-bit apps could runs slower due to more overheads. The only true usage for 64-bit cpu is to address the > 4GB memory limit, which Android is hitting the ceiling soon.
Looking at how long ago 64-bit desktop processors hit mainstream consumers, and yet an overwhelming majority of consumer desktop software has never really ventured much from 32-bit operation, I don't expect much from 64-bit mobile platforms.
Apple was so vague about how anything on their platform benefits from the 64-bit processor. But 64 is TWICE AS MUCH as 32, so of course it's better. Curious how much Samsung will implement anything different after deploying their own 64-bit processor. My money is on "not much."
Slapping a 64-bit cpu into a phone is not going to make existing codes runs any faster or better.
On Android, most apps are Java and "existing codes" are Java bytecode that get re-compiled on-the-fly to whatever the Java runtime is optimized for so, whether apps benefit from it or not depends mostly on how optimized the JRE's native recompiler, sandbox, native libraries, etc. are.
This isn't like PCs where most applications are compiled to native statically linked x86 code and require a re-compile by developers to include optimizations for new instruction sets, new libraries, etc.
64bit by itself is of limited benefit for a while in these devices (limited need in memory addressing or arithmetic). However, the ARM 64 bit instruction set is about as compact as it's 32bit predecessor, and includes a lot of optimisations (more registers, better SIMD). I recall that it also includes stuff that might assist with faster JIT for Android too. So even if you're not needing the 64 bit data size, there's lots of performance to be gained (but not because of 64 bit). In fact, it's a completely new instruction set implementation, not an extension of the 32 bit arm instruction set.
Why do people think Samsung copied Apple? Do you genuinely think they can design and, build and test this in a matter of weeks?
As has been said, ARM has had their 64-bit design for a while now. 64-bit has been in the pipelines in Samsung, Apple and probably Qualcomm and others for a while now.