Qualcomm Employee: Apple's 64-Bit A7 Chip 'Hit Us In The Gut'


Recommended Posts

Source: http://www.macrumors.com/2013/12/16/qualcomm-employee-64-bit-a7-chip-hit-us-in-the-gut/

 


"The 64-bit Apple chip hit us in the gut," says the Qualcomm employee. "Not just us, but everyone, really. We were slack-jawed, and stunned, and unprepared. It?s not that big a performance difference right now, since most current software won?t benefit. But in Spinal Tap terms it?s like, 32 more, and now everyone wants it."

[...]

"The roadmap for 64-bit was nowhere close to Apple?s, since no one thought it was that essential," the Qualcomm insider says. "The evolution was going to be steady. Sure, it?s neat, it?s the future, but it?s not really essential for conditions now."

But once Apple introduced a 64-bit processor, all the other phone-makers wanted one too. "Apple kicked everybody in the balls with this. It?s being downplayed, but it set off panic in the industry."

Basic psychology of want, not because I need, but because I want. Eg. I want what he has, just cause I don't have it.

 

Its like most analyst said: 64-bit makes little-to-no-difference but you can bet money that all the flag ship Android phones next year are going to be sporting it in response to Apple.

Its like most analyst said: 64-bit makes little-to-no-difference but you can bet money that all the flag ship Android phones next year are going to be sporting it in response to Apple.

 

This. If anyone argues so much about who does it first who does it right on here when it comes to Apple vs Android, it's me. Just like every release of an iDevice, how many Android devices have you seen try to follow a feature right after? HTC Fingerprint for example. Apple may not have done the fingerprint first, but they did it right which made others attempt to follow.

  • Like 1

Its like most analyst said: 64-bit makes little-to-no-difference but you can bet money that all the flag ship Android phones next year are going to be sporting it in response to Apple.

Pretty much.

 

Sad that when everyone else points out how useless at the moment 64 bit makes in smartphone OSes, they get bashed.

I can see that. Apple touted 64-bit goodness as a major selling point, and relevant or not, if other smartphones don't have 64-bit processors, they'll all be have-nots.

  • Like 2

It is the same old thing again. This situation is like, when you have two balls which look exactly the same and you will need the heavier in the future. Your friend drops the balls from a skyscraper and you are waiting for them on the ground. At this moment, as technology goes, the balls are still falling and there is no difference between them, but when they hit the ground and the software will begin to harness the benefits of 64 bit technology, you will need the heavy stuff.

 

Apple, yet again, tried to flash its E-penis and painted the ball red. Now everyone wants a falling red ball even if it does not matter. How easily distractable customers are. 64 bit is twice as much as 32, it must be soooooooooooo much better!

  • Like 1

It's hard to quantify just how much this will matter in a year or two. When AMD introduced 64-bit desktop CPUs it wasn't "needed" either but it jump started the industry and competition and soon after it was a necessity. 

  • Like 1

Basic psychology of want, not because I need, but because I want. Eg. I want what he has, just cause I don't have it.

Some of that is at play yes, but technology is also a chicken or egg industry...

 

What should come first? Software that needs 64bit or chips that support 64bit? See the conundrum?

 

Usually software waits for the hardware to exist before they start exploiting it. So the sooner we get 64bit hardware the sooner we'll get applications that take advantage of it. We can't accurately say if the advances will be useful or not yet because we don't yet have them...

  • Like 7

Its like most analyst said: 64-bit makes little-to-no-difference but you can bet money that all the flag ship Android phones next year are going to be sporting it in response to Apple.

 

Samsung already announced 64bit.  But this is normal no matter what industry you work in.  Someone produces something, others find value and add it to their products.

Its like most analyst said: 64-bit makes little-to-no-difference but you can bet money that all the flag ship Android phones next year are going to be sporting it in response to Apple.

and then Windows Phone will be reviewed poorly for using "only" 32bit processors. :laugh:

This. If anyone argues so much about who does it first who does it right on here when it comes to Apple vs Android, it's me. Just like every release of an iDevice, how many Android devices have you seen try to follow a feature right after? HTC Fingerprint for example. Apple may not have done the fingerprint first, but they did it right which made others attempt to follow.

My Motorola Atrix finger print worked fine.  2 years before the iPhone 5.

  • Like 3

My Motorola Atrix finger print worked fine.  2 years before the iPhone 5.

 

I don't think his point was that Apple came out with a fingerprint reader on their phone first.  His point was that your Motorola Atrix introducing the feature didn't mean squat to other Android manufacturers.  Once Apple released the iPhone 5S with a fingerprint reader there was a sharp 'me too' response almost immediately from the Android OEMs.

  • Like 2

Even quad cores are overkill.  64 bit is getting ready for when phones need more then 4 gigabytes in memory. 

You do realize that 64-bit has more advantages than just memory capacity, right?...

  • Like 1

I'm not an Apple fan at all. I hate their "Walled Garden" and one size fits all designs but I have to hand it to them. I'd love an A7 SoC in a phone I actually liked.

As for those saying 64bit doesn't make a difference it's true there isn't much, if any improvement (in some cases things may even slow down) simply by going 32bit to 64bit. The ARMv8 architecture isn't just an ARMv7 with 64bit tacked on though and it DOES have substantial speed improvements even when running just 32bit software. ARM really took this opportunity to clean up and fine tune their design and it paid off.

Apple really is ahead of the game in SoC design and 64bit OS support (their entire OS and all it's built-in apps have 64bit versions already) so that's a big win for them. They need it though because iOS apps are native code and everything needs to be recompiled to support 64bit. That's going to be a HUGE and long transition for them. In contrast since Android and Windows Phone compile to byte-code unless developers wrote parts in native code (NDK on Android, not sure if Windows Phone has an equivalent) they have to do nothing. The 64bit JIT engine provided by the OS will automatically compile their byte-code application 64bit. This means the migration to 64bit will take much less time on Android/Windows Phone so it's good Apple has a head start to stay competitive (competition is good for us consumers)

I'm not an Apple fan at all. I hate their "Walled Garden" and one size fits all designs but I have to hand it to them. I'd love an A7 SoC in a phone I actually liked.

As for those saying 64bit doesn't make a difference it's true there isn't much, if any improvement (in some cases things may even slow down) simply by going 32bit to 64bit. The ARMv8 architecture isn't just an ARMv7 with 64bit tacked on though and it DOES have substantial speed improvements even when running just 32bit software. ARM really took this opportunity to clean up and fine tune their design and it paid off.

Apple really is ahead of the game in SoC design and 64bit OS support (their entire OS and all it's built-in apps have 64bit versions already) so that's a big win for them. They need it though because iOS apps are native code and everything needs to be recompiled to support 64bit. That's going to be a HUGE and long transition for them. In contrast since Android and Windows Phone compile to byte-code unless developers wrote parts in native code (NDK on Android, not sure if Windows Phone has an equivalent) they have to do nothing. The 64bit JIT engine provided by the OS will automatically compile their byte-code application 64bit. This means the migration to 64bit will take much less time on Android/Windows Phone so it's good Apple has a head start to stay competitive (competition is good for us consumers)

 

I used to think Android apps were less native due to the fragmentations and whatnot. It may be quicker, but it'll still be hard to get it to roll out on all the devices out there like Apple can.

I used to think Android apps were less native due to the fragmentations and whatnot. It may be quicker, but it'll still be hard to get it to roll out on all the devices out there like Apple can.

Android apps are "less native" so the same app can run on multiple different architectures. This is why you can have an app that runs on an ARM based phone as well as an Intel based one (completely different architecture). More new ones are even on the way with Imagination Technologies (people who make the PowerVR GPUs used by Apple and others) having bought MIPS expect to see devices running MIPS/PowerVR SoCs in a 2014/2015. Google does it this way because they don't make their own hardware and they want to be able to use whatever is best at any given moment and not be stuck to one architecture. It works in their favor for the 32 to 64 bit transition as well. The hard work is done in the JIT compiler provided by the OS instead of every app having to be recompiled. That work is typically done by the hardware manufacturers, for example Intel has been checking in a lot of code to the Android codebase to get 64bit working on their processors. Once that is complete any OEM making an android phone with an Intel SoC will use the Intel provided JIT compiler and app developers will have to do nothing. The exception being if the app uses the NDK (native development kit) in which case it has architecture specific native code and the app developer will need to recompile the NDK parts for every architecture they wish to support (just as Apple app devs will have to).

On a side note Android is also making a AOT (Ahead of Time) compiler called ART (Android Run-Time) to replace the Dalvik JIT engine so that apps compile from byte code to native code on install instead of on run. If you are familiar with .Net this is similar to the NGEN tool that .Net has which apps like Paint.Net use on install.

So you are saying that 64-bit is more useful with 512MB memory as a whole, than 32-bit with 2GB memory?

Uh...where are you drawing that conclusion from?  The point is that the amount of memory doesn't matter.

Yes, you can use more than 3.5GB of memory with 64-bit, but that's only one of many advantages.

A major benefit is security.  

 

Educate yourself on why a 64-bit instruction set is very beneficial.  There's a lot of information out there.

Apple leads the way....once again.

I wouldn't say leading, as it would if ATM it were a meaningful advantage, like pointed above, 64 IS the future, but in 2-3 years. Heck we've barely transitioned into 64 bit on desktops.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • You've tried DuckDuckGo and Brave Search, now get serious with SearXNG by Paul Hill Over the last decade, it has become quite trendy to dump Google Search in favor of privacy-preserving alternatives such as DuckDuckGo, Startpage, and Brave Search. These search engines have done a very good job at highlighting dodgy practices by Google, such as adjusting search results based on what it thinks you’ll like (filter bubble) and stalking you around the web to advertise to you. While these search engines are good starting points when compared to non-private services like Google, there are still quite a few issues with them. For example, both DuckDuckGo and Brave Search require running non-free JavaScript in your web browser, which is comparable to running proprietary software on your computer, meaning you can be sure about what it’s actually doing in the background. Another issue is that these search engines are hosted on the respective companies’ servers, and you are using a service that you don’t control. Finally, DuckDuckGo, while offering privacy features, relies heavily on Microsoft’s infrastructure for its results and, in the past, has permitted Microsoft tracking scripts. If you are looking for a more private search solution than DuckDuckGo, Brave Search, and Startpage, then I recommend taking a look at SearXNG. It is a privacy-respecting metasearch engine that can be used via different public instances, which is useful for mobile users, or you can install it on your computer or server and run it locally with maximum control. Unlike Google, Bing, or Brave Search, which crawl the web and have their own search indexes, SearXNG is a metasearch engine, meaning it taps other search engines, stripping your identifying data, such as IP address, user agent, and cookies, in the process. Your search query is sent to the other search engines you enable before aggregating the results. SearXNG has deployment flexibility. If you are a casual user or a mobile user and don’t want to run SearXNG locally, you can use a public instance that is hosted by someone else. The main problem with this is that you are putting trust in the maintainer of the instance regarding stuff like logs that they may keep; good hosts should have a privacy policy explaining their policies. If you are trying to use SearXNG, you can also install the software on your device and then head to 127.0.0.1:8080 in your browser and search from there. While you don’t have to worry about a third-party admin like the public instances, search engines could ultimately block your IP address if they frown on you pulling in their search results locally. If you want to run it locally, it’s a good idea to use proxies or VPNs to hide your actual IP. You don’t have to worry about this with a public instance, as search engines never see your IP address. The main privacy benefit of using SearXNG is that it isolates your identity from the underlying engines that it’s capable of searching, such as Google and Bing. These search engines will only see requests coming from a generic server, so they can’t profile you and create a bubble filter that influences what results you see. This also ensures that your search engine doesn’t turn into an echo chamber that prevents you from reading alternative points of view. As a free software project, you are allowed to inspect SearXNG to make sure there are no negative features bundled inside. This sets it apart from the privacy search engines mentioned earlier because you can’t check their source code. As a meta search engine, you are not restricted to getting results from one source. Due to the fact that it scrapes content from other websites, your SearXNG instance will periodically get blocked from different providers, so it’s good to select a range of sources as a backup. While enabling all of the services will give you great results, this can make searching slower. I am personally happy with slower searches for the best results, but you can always check which providers are slowing down your search from the search results page and disable them to speed things up. If you want decent results quickly, enable the main search providers such as Google, Brave, DuckDuckGo, Qwant, Bing, and Yahoo. This way, you get wide coverage without the latency. On the Engines tab in Preferences, do note that there are different tabs, such as General, Images, and Videos, with their own providers that can be toggled and are not covered by "Enable all" while on the General tab, so be sure to dig into each. Just a note, if you want to enable everything, press "Enable all" in one tab, then hit save at the bottom of the page, then do the next tab, and so on. If you press "Enable all", then do that in each tab, and then save, nothing will stick. When I had just some of the search engines enabled, I searched “define nefarious” and results came back with the definition of “define” - obviously that was a sucky result. However, when I had everything enabled, it found dictionary pages for the word “nefarious” and even had an inline definition on the sidebar, which is quite nice too - that was delivered by WolframAlpha for anyone wondering! Probably the worst thing about this meta search engine is that the engines you select are saved with a cookie, so you must enable them on every new device you use SearXNG on, including if you decide to go into incognito mode with your web browser. Honestly, I would say this is the most annoying aspect, and perhaps if your browser lets you choose a separate private browsing search engine, then it would be best to use DuckDuckGo for this portion of your browsing. Another weakness of SearXNG is the random blocking of it by search providers. When you are on the results page, expand the “Response time” box, and it will show things like “Suspended: too many requests” or “access denied”. This is why it is good to enable several providers so that there is always a fallback to get results from. I won’t pretend SearXNG will be for everyone, however, if you enable all of the providers and put up with the slower response time, the results can be really amazing. Even if you don’t want to use it as your daily driver, keeping a bookmark handy that links to it is a good idea if you ever feel like doing a deep dive into a niche topic where other search engines are just failing to bring up any good result, due to the amount of sources it looks on. If you’re interested in radical user control over the software you use, installing SearXNG locally can also be a good idea, but be prepared to be temporarily blocked from sites if you trigger bot sensors without a VPN. Personally, I’ve opted to use a public instance, rather than install it myself. If you want to use it via a public instance, head over to searx.space to find a provider. Let us know in the comments if you have used SearXNG or its predecessor, Searx. What do you think about the quality of the results?
    • Dear Neowin, If it is not too much trouble, can you start using the new-ish designations for Insider Preview? "Experimental" is different than "former Dev" as it can apply to different models, eg 26H1 or 26H2 etc, right? No need to seed confusion IMHO. And, please "finally" update your graphics. OK?
    • Did you see their FAQ, its quite good. Have a look in the Advanced section. https://delta.chat/en/help
    • Just install Linux Mint that is a real blessing and many times cheaper because you can continue using your old Windows computer/laptop with the latest Linux updates.
    • Interesting share -- however it does not make sense: Email messages get stored somewhere, so how is Delta Chat "based on email" and decentralized without actually storing anything? By Web3 standard practices, the various Relays would require dedicated storage to make messages available to the recipients (like a large series of message queue channels, akin to racks of traditional post office boxes)... and Contacts must be two-way confirmed in order for encryption keys to be exchanged (ostensibly every key-pair is uniquely bound between sender and recipient) and the Relays would preserve the public keys in order to facilitate message carriage... or every device stores all sorts of keys and contact info. All of this to say, decentralized messaging is like running Bluesky nodes except instead of discovering/browsing public feeds by various posters (at the given node) these Delta Chats would be relaying encrypted messages (via Relays) that only trusted recipients would have the appropriate decryption key (their own private key) to read it. But this doesn't solve the "it's like email" sales pitch. The only way it's like email is that there's encrypted binary stuff being transported from your app into the federated ether of Delta Chat Relays for others to decrypt (hopefully only the intended recipient)... but outside of this federated relays framework, it is absolutely nothing like email.
  • Recent Achievements

    • Week One Done
      Woland13 earned a badge
      Week One Done
    • One Month Later
      Woland13 earned a badge
      One Month Later
    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
    • Week One Done
      tuben earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      503
    2. 2
      +Edouard
      226
    3. 3
      PsYcHoKiLLa
      158
    4. 4
      Steven P.
      75
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!