Nexus 5 With Android 4.4 and Snapdragon 800 Challenges Apple A7 In Benchmarks
MojoKid writes "One of the hallmark features of Google's Nexus 5 flagship smartphone by LG isn't its bodaciously big 5-inch HD display, its 8MP camera, or its "OK Google" voice commands. That has all been done before. What does stand out about the Nexus 5 is Google's new Android 4.4 Kit Kat OS and LG's SoC (System on Chip) processor of choice, namely Qualcomm's Snapdragon 800 quad-core. Qualcomm is known for licensing ARM core technology and making it their own; and Qualcomm's latest Krait 400 quad-core along with the Adreno 330 GPU that comprise the Snapdragon 800, is a powerful beast. Google also has taken the scalpel to Kit Kat in all the right places, whittling down the overall footprint of the OS, so it's more efficient on lower-end devices and also offers faster multitasking. Specifically memory usage has been optimized in a number of areas. Couple these OS tweaks with Qualcomm's Snapdragon 800 and you end up with a smartphone that hugs the corners and lights 'em up on the straights. Putting the Nexus 5 through its paces, it turns out preliminary figures are promising. In fact, the Nexus 5 actually was able to surpass the iPhone 5s with Apple's 64-bit A7 processor in a few tests and goes toe to toe with it in gaming and graphics." Ars Technica has a similarly positive view of the hardware aspects of the phone, dinging it slightly for its camera but otherwise finding little to fault.
This is not a fair comparison, the iPhone is twice the price.
Well it's actually worse than that. A phone that has a SoC with double the cores, cores that have a max clock rate 1 ghz higher and double the memory is only able to win in a couple of tests and just keep up with the A7 in every other test. Sounds like pretty fail.
Now now that shit will get you down-modded here (as will this post, most likely). because here at slashdot we're all about software efficiency, not that bloated microsoft shit.
Owait..
Sooner or later, Google are going to have to admit that using a JVM was a bad idea. JVMs have been fail on the desktop since the mid 90s, and waiting for hardware to catch up has proven to be a mistake - especially in mobile. More cycles = more power = bigger battery required = more weight.
I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
So the screen resolution is why it was faster in Sunspider and Browsermark? Also in the off-screen GPU test (of which screen resolution makes no difference) it was only 10% slower which makes sense since the GPU cores on the Snapdragon 800 are clocked faster.
Uh... Apple has never pushed numbers. Try and find in any of their keynotes any mention of iphone screen res numbers, CPU clockspeed, etc?
Apple build hardware to do a job. At the screen size the iphone runs, the resolution it runs, at the typical use distance is plenty. Pushing any more pixels around on that device is pointless. So why do it? "Oh but it's not full HD!". On a screen that size, this point is irrelevant.
I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
To add even in the offscreen test done by Anandtech here against the Note III it only lost by 1 fps in 2 of the tests as in another it was 12 fps behind. But, in the test it was 12 fps lower it was 57 fps to 69 fps which means that basically it was only 5% lower than screen refresh rate.
They are both very nice phones. There. I said it.
Help stamp out iliturcy.
Qualcomm's latest Krait 400 quad-core along with the Adreno 330 GPU that comprise the Snapdragon 800, is a powerful beast.
If they had not focused much on the specs, but rather on battery life that can last a day of average use, I'd be happier. I ask my self: -
"Of what use is having the"latest and greatest if by mid-afternoon, I will be holding a brick in hand?
This is what I do to these good phones that are limited in the battery department. I underclock them with acceptable results.
By the way: Can one explain to me how Motorola was able to cram a 3000mAH into a phone smaller than this but Google and its LG partner cannot?
Got them running a lot of apps on a lot of hardware quickly though. Now things are settling, I'd imagine this new ART core will be improved on to keep trimming performance up and reducing battery drain. It's done the job it was designed for pretty well so far.
Waiting for an amusing sig.
The physics test is quite telling and shows just how limited the low speed, dual core
The physics test seems to have little relevance to actual gaming performance since even against the Note III in offscreen tests the iPhone 5S was pretty much neck and neck on rendering rate.
http://www.anandtech.com/show/7376/samsung-galaxy-note-3-review/4
In that review the iPhone 5S won 4 of the 7 CPU tests that it was in. It won 3 of the 6 GPU tests measuring FPS rendering speed. In 2 of the tests that it lost it only lost by 1 fps, in the other offscreen test that it lost at it was 57 fps vs. 69 fps. Which means the 5S was only 5% slower than native refresh rate.
dual core? really? that is fucking ancient) CPU in the iPhone is.
And yet it beat the quad-core in both of the CPU tests. Can't even beat an "ancient" CPU? Pathetic...
Actually I noticed the 5S release was different (for Apple) in that very respect - they trumpeted very little besides behind-the-scenes specs. 64 bit! New co-processors! Look at these benchmark graphs!
Actually, their last keynote did mention that sort of thing. 64 bit?
Shame...
So can get a supported version of Kit Kat on all past versions of my Nexus Phones?
the article doesn't touch on this, but I wonder how much untapped power is in that 64bit processor in iPhone. what's cool is, that's dormant in my phone right now, but will be unleashed next year so it will be like getting a new phone.
No it didn't, it only scored a pathetic 7431 in physics compared to more than twice that amount for the Nexus 5. iPhone 5 got its ass handed to it due to the weak CPU in it.
NSA/Google fucking sucks.
... something better than my old HTC 3G EVO that runs latest android for a decent price? I'm switching to Ting and don't mind buying behind the curve, but it's not easy to get something at the same budget I'm used to when I get the phone(s) mostly subsidized from Sprint. Maybe I'm looking at the wrong review sites to find a peppy cheap android.
Horror & SciFi Erotic Nudes
New phone almost as fast as month old phone.
Xperia Z1 was released same day as iPhone 5s. It is faster, waterproof, and has higher res 1080 screen. It also has a 20.7MP camera with a much larger 1/2.3" sensor.
Android already supports applications using native code. But a lot of apps just don't need it.
The original iPhone caught on because it could play DRM iTunes.
You know, I don't think I've ever seen as horribly misguided a reason for the adoption of the iPhone as that one.
By your logic, the Motorola ROKR would have been a smash hit.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
the article doesn't touch on this, but I wonder how much untapped power is in that 64bit processor in iPhone. what's cool is, that's dormant in my phone right now, but will be unleashed next year so it will be like getting a new phone.
Please tell me you're being sarcastic... Even if all your apps get recompiled to 64-bit versions, you are not going to get a massive performance boost. Have you ever tried running a 32 vs. 64 bit install of Windows or Linux on the same hardware? Not too much difference for average use cases...
Android Apps are actually portable (unlike iPhone apps)
Given the screen sizes of modern Android phones I'd say iPhone apps are actually quite a lot more portable. :-)
less hostile to develop for
Because good tooling is inherently bad for your health, just like using hammers is far inferior to the strength-building task of pounding in nails with railroad ties.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
We ran Sunspider (1.0.2).
The iPhone 5S (and a Nokia Lumia 920) pasted my Nexus 5 on Sunspider. Both were about twice as fast as the Nexus 5.
I like the Nexus 5, it's very snappy. But when using it, it doesn't feel faster than a 5S.
The N5 is a heck of a value.
Now, about the awful pictures it takes... Is there any chance a better camera app (which also sucks) can improve them some?
http://lkml.org/lkml/2005/8/20/95
iPhone 5 got its ass handed to it due to the weak CPU in it.
Weak CPU, or weak physics engine that didn't use OpenCL or the Accelerate framework...
In fact the benchmark technical guide says explicitly:
The GPU load is kept as low as possible to ensure that only the CPUâ(TM)s capabilities are stressed.
Which is a really stupid way to compare things as anything that relied on advanced physics would be using some kind of accelerator for computation other than the CPU. It also means it's not using any of the real-world physics engines a game would be using.
Sure the iPhone Physics score will be down a lot if you tie both hands behind its back and throw it in a river.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
Yeah but that phone is half the price of the iPhone.
Pretty impressive to me.
Mod me down, my New Earth Global Warmingist friends!
yeah but if you use your iphone as a media transcoding server, the gains with be iMazing!
Mod me down, my New Earth Global Warmingist friends!
64 bit is a bit different to e-peen measuring with clockspeed numbers or screen resolution numbers. 64 bit is a significant step, not just "this is better because the number is teh bigggar!!"
I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
Yeah because when I am out and about, i much prefer to carrry a map, a compass, a walkman, a mobile phone, a laptop, a pager, a camera, a tape recorder and a gaming console. Fuck those integration guys in the neck.
I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
I've heard people claiming "oh but wait until XXXX, you won't need to write native code anymore!" regarding Java performance for ages. Since 1996. Java still sucks compared to native code.
I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
So can get a supported version of Kit Kat on all past versions of my Nexus Phones?
Google said there's an 18 month update window, and anything Nexus than the Nexus 4 (like the Galaxy Nexus) won't get Kitkat:
https://support.google.com/nexus/answer/3468085
Is Google releasing Android 4.4 as a system update for Galaxy Nexus?
No, Galaxy Nexus phones won’t be receiving the update for Android 4.4 (KitKat).
Why isn’t Galaxy Nexus receiving the update to Android 4.4?
Galaxy Nexus, which first launched two years ago, falls outside of the 18-month update window when Google and others traditionally update devices.
Yup, because burning CPU cycles at twice the rate to run "fast enough" is the way to awesome battery life.
I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
Not really. They still had to do an SDK for the phone, they could just as easily written an SDK for native code rather than Java. I suspect use of Java was a hedge against either ARM or Intel providing the better mobile CPUs, whereas apple made the decision and bet on ARM.
I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
The iPhone might not be any better (I don't know and don't care) but that's fucking pathetic.
Weird thing is the way android is headed, apps will be compiled via llvm to native code (its an option with kitkat now and will be default at some point in the future). It's just done at install time so that android can run on any cpu instead of at compile time.
omg, larger numbers!
Sony could release a phone that claimed to cure cancer, solve world poverty and establish peace in the middle east. They're still not getting a cent of my disposable income.
I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
Java has always been meant to be an underperforming hog to justify new hardware sale for Sun corp.
The iPhone might not be any better (I don't know and don't care) but that's fucking pathetic.
As a Galaxy Nexus owner (who just bought a Nexus 5) I agree, an 18 month update window is pretty bad in an industry where 2 year contracts are common. There is a petition to get Google to release Kitkat for the Galaxy Nexus, but behind the scenes, Google is blaming it on TI:
http://news.cnet.com/8301-1035_3-57610844-94/galaxy-nexus-owners-petition-for-taste-of-kitkat/
JVM should have been optional on Android, just like anywhere else.
iZealots like to boast numbers
Funny. This has to be the first time I've seen iPhone fanboys accused of being the number folks by Android fanboys.
And one with private parts possessing a particularly desirable physical attribute.
It makes no difference to battery life; almost all the battery usage on Android phones goes to the display and the radio. And CPU-bound applications (e.g., PhotoSphere) are written using native code anyway.
Why is it a significant step? What does it actually _give_ you as a phone user?
It's an irrelevant detail.
... crapware phone. If that is all you have done, and you are down to 58% then you have nothing but crapware.
When it comes to taking photos, the key is in the lens. Cheap lens will produce crappy images no matter how much you auto-photoshop them.
whereas apple made the decision and bet on ARM.
Apple has experience and proven track record in quickly changing archs. If anything new cpu arch would mean more money for them - forced upgrade cycle in ecosystem where users currently upgrade almost only when old stuff breaks or new one looks nicer.
Who logs in to gdm? Not I, said the duck.
The Nexus comes with only 18 months of support.
KatKrap isn't broadly available.
http://www.mikeash.com/pyblog/friday-qa-2013-09-27-arm64-and-you.html
If you actually RTF, you'll see the 5s wasn't tested uniformly but it killed the Nexus 5 in several performance tests, including battery life.
I have owned iPhones since the iPhone4. I currently own the iPhone 5. My wife owns the Nexus 5. I can tell you that there is *** NO LAG *** on either the Nexus 5 or the iPhone 5. They are equally fast, both very smooth and instantaneous response times. Both phones are very, very sweet.
The iPhone 5 presentation is slightly nicer, but for the price??? The Nexus 5 is king. There is NO comparison. When you consider the cost difference, Apple gets kicked to the curb.
My initial thoughts? I love the new IOS7 - particularly the new control center - where I can easily turn off my WIFI when away from home, to save battery life. But I love Android's ability to just copy your song collection where you want, when you want. I FUCKING HATE HATE HATE iTunes with a passion - it makes Windows 8 look like an Adonis. If they made a vaccum cleaner suck as hard as iTunes does, you'd have cornered the market and destroyed all competition. It really is that much of a steaming pile of shit. Kill it with fire. iTunes is about the only Achilles heel left for Apple.
They talked about the fingerprint reader, the secure storage and how the new M7 processor will give you better battery life. These are real things that impact customers. Didn't they talk about faster LTE throughput too? Maybe I misremembered.
It wasn't just specs.
http://lkml.org/lkml/2005/8/20/95
That's why they are switching to ART.
The iPhone might not be any better (I don't know and don't care) but that's fucking pathetic.
iPhone 3GS shipped with iOS 3.0 in June 17, 2009.
Final iOS update was 6.1.3 in March 19, 2013.
http://en.wikipedia.org/wiki/IOS_version_history
That is 45 months. (Past performance does not guarantee future results.)
Then explain why these benchmarks show that with about 2x the CPU hardware, the Nexus5 is not comprehensively beating the crap out of the iPhone.
I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
Please recommend good applications. I bought a Nexus 5, because I recently dropped my previous smartphone. But what do I do with it?
Google also has taken the scalpel to Kit Kat in all the right places, whittling down the overall footprint of the OS
What was problem with Linux in Android 4.3? Operating System footprint was very small, just ~300KB of storage and little over 1MB of RAM. So seriously, how much they really got down Linux operating system footprint in Android 4.4 as it gains so much notice?
Native in this case means C or C++......
It's even simpler than that. Upgrade to Xcode 5, do a Archive build to send it to the App Store and it'll include a 64 bit version with no programmer intervention. Apple is really confident in the compatibility of their LLVM builds. If nothing else, you should get in the habit of testing in the 64 bit simulator until you get an A7 device.
Yeah, that is the reason. The OMAP programme is simply gone - everyone's been sacked, and they've all been EOLed. Ti's drivers are closed, and with no official support, and no source release, there's no-one to update them for any version of Linux past 3.0 (someone's got them booting - barely - on 3.4, but you can forget 3.13).
You can see it in the AOSP builds, which you definitely can build for the maguro - it's all good, except the graphics, which periodically corrupt (especially in screen rotations) and after a while that causes the GPU to freeze, the watchdog kicks in and the phone resets.
You CAN run KitKat on the Galaxy Nexus, but it's not stable - and it will take a LOT of work to get it stable - possibly work modifying or working around blind binary blobs. (This is yet another reason why blind binary blobs are bad.)
I'm waiting past the Nexus 5: non-removable battery in a developer phone is an absolute dealbreaker. What if I get an Oops and the watchdog doesn't kick in? That happens maybe twice a month for me... plus what I do requires batteries out of phones sometimes - which mandates phones with removable batteries, period.
I want an ARMv8 in my phone, whether it be a Cortex or Qualcomm's take on it (Apple's is actually a surprisingly vanilla, machine-laid-out, first pass). I dearly hope that things settle down a bit so the ARMv8 SoCs don't have the terrible problem previous versions did with kludgey hardware support and needing out-of-tree Linux forks.
I doesn't have "2x the CPU hardware"; the number of cores bears little relationship to the amount of "CPU hardware" a chip has. For mobile systems, people often use more cores but slower cores to save battery life, because for most tasks only one core needs to be activated. You'd use all cores only on compute-intensive tasks. And for benchmark comparisons, it gets even trickier because some benchmarks may be able to take advantage of lots of slow cores, while others prefer fewer faster cores. In the end, what really matters is the price/performance on real software, and the Nexus 5 certainly "beats the crap" out of the iPhone in that regard, giving you similar performance at a fraction of the price. (FWIW, I think both Java and Objective-C suck, but that's an entirely different discussion.)
> "and Qualcomm's latest Krait 400 quad-core"
That's better than Apple's latest Kreetle 400 duo-core!
(-1: Post disagrees with my already-settled worldview) is not a valid mod option.
Now waiting for a price. Hope it shouldn't cost as much as Iphone.
Yeah because when I am out and about, i much prefer to carrry a map, a compass, a walkman, a mobile phone, a laptop, a pager, a camera, a tape recorder and a gaming console.
I am curious ...
...
Before 2011, did you regularly go out and about with a map, a compass, a walkman, a mobile phone, a laptop, a pager, a camera, a tape recorder _and_ a gaming console ?
Don't get me wrong, I'm just curious
Muchas Gracias, Señor Edward Snowden !
Every purchase has an emotional dimension. Judging by my friends who own iPhones, I'd say it is considerably higher than average in this case. One even said he decided not to buy another iPhone, but went ahead and did it anyway. He couldn't explain why, and seemed totally happy with that.
No, it's not a phone. It's a pocket-sized computer that can also make phone calls. We call it a smartphone for historical reasons. Do you also complain that we say 'computer' as shorthand for 'electronic computer', when we all know that a computer is a person who prepares logarithm tables?
I am TheRaven on Soylent News
Sony could release a phone that claimed to cure cancer, solve world poverty and establish peace in the middle east. They're still not getting a cent of my disposable income.
Well aren't you a selfish bastard. We must think of the children!
More importantly, will it run Linux? And for how long?
May have got 6 bit didn't get all the features including tethering. So a Clayton's update.
I find it hilarious that they are trying to benchmark CPUs using javascript on *different* browsers. Do they not realise that the javascript performance of Chrome is radically different than Safari?
I am curious...
Before the 20th Century did the average person drive an automobile?
Before the Industrial Revolution did the average person have access to cheap, mass produced good?
Before the Agricultural Revolution, did the average person have access to plentiful grain?
Before the Paleolithic, did the average person have access to crafted stone tools?
Don't get me wrong, I'm just curious...
The main advantage of 64 bitness is access to a far larger memory address space. Yes there can be a few minor performance improvements with proper use of larger registers, but it's really not that big an advantage. Until smartphones and tablets start exceeding 4 gigabytes of RAM there is really not much point other than marketing to use 64 bit code on such devices.
The main advantage of 64 bitness is access to a far larger memory address space. Yes there can be a few minor performance improvements with proper use of larger registers, but it's really not that big an advantage. Until smartphones and tablets start exceeding 4 gigabytes of RAM there is really not much point other than marketing to use 64 bit code on such devices.
That has been debunked again and again and again.
There has been iOS code that was measured to be 45% faster just by being recompiled to 64 bit. There are plenty of tricks in the Objective-C runtime and the C++ libraries that make it _significantly_ more efficient when running on a 64 bit processor. For example, a std::string up to 22 chars doesn't allocate any memory on the heap in 64 bit code but just uses three 64 bit words.
Do you actually trust Android benchmarks? Or benchmarks in general?
lots of people claimed that it didn't really matter because nobody is interested in benchmarks. And now we have this whole article and huge discussions because of benchmark results. Quite interesting.
Any opinions whether benchmarks matter or not are welcome. On the other hand, there was an old joke about a potential customer asking what was the horse power and top speed of a Rolls Royce. Answer: "Enough".
That's what "native" means in every case. Android supports C/C++ programming.
After using an Xperia S for the last year and a half, I tend to agree but waterproof with a much better camera...
if you, as a company specializing in soc design, cant crush a chip released half a year ago, you should step up your game. especially when the number of chips you move is so high. apple did a "by-hand" design. if thats what it takes to maximize power efficiency and performance, do that. but do it better. if i buy a tent made by Jeep (yes, i really used to own one), or a television made by Ford (yes, my neighbor did back in 1994 maybe) i will not expect it be as good as proper specialty team designed products
More and more people are feeling that way about apple. Bill Gates a great humanitarian, Steve Jobs an asshole.
Where is the Nexus 5 half the price? Everyone is selling the Nexus 5 for $350 with contract while the iPhone 5s is $200 with contract.
my karma will be here long after I'm gone
With Sony I can move to different phones without losing any of my music, movies or data. They are not locking me down if I disagree with their practices or corporation actions!
No, it's not a phone. It's a pocket-sized computer that can also make phone calls. We call it a smartphone for historical reasons. Do you also complain that we say 'computer' as shorthand for 'electronic computer', when we all know that a computer is a person who prepares logarithm tables?
Yes, yes, so much yes. My smartphone is hardly used in the phone-kind of way (not much of a caller anyway, hardly touch those 'free' minutes) but as an internet-computer/pdf-viewer/musicplayer/calculator/watch SO much more. It doesn't do any of those functions really well, but just good enough and the fact that it's all in one single handheld device makes me happy.
When I ONLY want a good mobile phone I'll get my old trusty Siemens.
All those moments will be lost in time, like tears in rain. Time to die.
Where is the Nexus 5 half the price? Everyone is selling the Nexus 5 for $350 with contract while the iPhone 5s is $200 with contract.
Incorrect.
The Nexus 5 is $350 for the one with 16GB of space, $400 for the 32GB one, and that is with NO contract.
iPhone 5s is only $200 with a contact, if you want to buy it outright without a contract, it costs $650 for 16GB and $750 for 32 GB.
In other words, about 1/2 the price.
Then explain why these benchmarks show that with about 2x the CPU hardware, the Nexus5 is not comprehensively beating the crap out of the iPhone.
Because obviously you are a wittless moron that doesn't know the first thing about... well judging by your posts... anything.
All of those benchmarks are not designed to use multiple cores..... So it doesn't matter if I have 4 or 400 cores, it is not going to make the bench marks work any faster. So it has double the cores than the iphone big deal, it doesn't matter in the benchmarks. On the other hand it does matter if you are running multiple applications at once (or services in the background).
My major p is to have tool whoose power house can serve.. else it equals crap!!! Something Similar
Except that Android doesn't have JVM.
Dalvik is a virtual machine and sandbox. You can write native C and C++ code what gets executed in native speeds without any penalty from any virtual machine (read Dalvik). Meaning you write a software what only needs packed as APK and few dozen of lines code with java what is about how application is shown in launcher etc.
The main advantage of 64 bitness is access to a far larger memory address space. Yes there can be a few minor performance improvements with proper use of larger registers, but it's really not that big an advantage. Until smartphones and tablets start exceeding 4 gigabytes of RAM there is really not much point other than marketing to use 64 bit code on such devices.
Oh c'mon. Slashdot is supposed to be the smart nerds.
One advantage of a 64 bit architecture (such as x86_64 or the A7) is that in order to hold 64 bit data. But if you're still working with 32 bit data (and most of us are), you can simply load each register with two 32 bit chunks, basically doubling the amount of data you can hold on chip, and the processor has functions to support this.
And if you look at what Apple did with the A7, not only does their 64 bit chip do this, but the new ARM64 specifications double the number of registers in general:
"The ARMv8-A instruction set doubles the number of registers of the A7 compared to the ARMv7 used in A6.[13] It now has 31 general purpose registers that are each 64-bits wide and 32 floating-point/NEON registers that are each 128-bits wide."
http://en.wikipedia.org/wiki/Apple_A7
So basically you now have an crazy amount of registers, and an insane amount of registers if you are dealing with 32 bit data still. The NEON registers are 128-bits wide and there are 32 of them. If you have 32 bit data, you can process 128 chunks at a time! If you're working in float_16 with NEON, you can work through 256 chunks at a time. That's crazy good compared to ARM32. That would really speed up anything that works with media, images, video, animations, etc, most of which a modern window server does.
But that's not really the end of optimizations. If your registers are large enough, why bother using pointers? And that's what Apple did with the Objective-C runtime on ARM64.
http://www.mikeash.com/pyblog/friday-qa-2012-07-27-lets-build-tagged-pointers.html
Basically, if you've got a small enough object type, like an object that holds an 32 bit type, you can skip the allocation of extra memory to hold this data, and just store it in the pointer itself. A lot of the low level and frequently hit methods in Obj-C (like the entire memory allocation tracking system) have been optimized for this, so you should see a speedup in even basic applications.
With apple I can move to different phones without losing any of my music, movies or data. Sony get a big thumbs down based on their treatment of customers in the past - reneging on PS3 OtherOS support post-sale, installing the cd-rootkit on Windows machines, their massive fail at online service security and being coy about the extent of their break in, etc.
I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
Your argument falls apart the second you realize the Nexus has BOTH more cores AND faster cores.
Whoosh. But no, I had to deal with paper based maps, guess at direction, not be able to check on things at work away from my desk, fail at documentation (convenient video/audio/photos = awesome) and basically be bored out of my brain on public transport.
I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
Exactly. Until a mandatory firmware update some time after purchase.
I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
My reasons for hating sony have zero to do with humanitarian stuff. And besides, have you forgotten about product red, which has been going on for well... a decade or so at a guess?
I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
Hell, Apple and iOS developers have been compiling for Intel architectures from the beginning: the iOS simulator that runs on the Mac is not an ARM emulator; Xcode compiles intel-native binaries for it.
cool explanation bro, but if so why isn't the i5s already crazy stupid faster than nexus 5?
cool explanation bro, but if so why isn't the i5s already crazy stupid faster than nexus 5?
A few reasons. The A7 is a dual core chip at 1.3 ghz. The Nexus 5 is a 2.3 ghz quad core chip. So basically Apple is fighting with brains and LG/Google are fighting with brawn.
There are a few reasons Apple's approach is probably smarter. First, the more you increase a chip's clock speed, the more power it's going to consume. Apple is taking the strategy of basically keeping the clock speed constant but making the chip more efficient, hopefully keeping energy usage in check. The Nexus 5's fast clock speed doesn't pan out so badly because it's a larger device with a larger battery, but in the long term it's probably not sustainable.
The other thing Apple has going in it's favor is that in order to get the power out of the Nexus 5 processor, you've really got to get your app optimized for quad core, which isn't very common. Most apps are single or dual core, both of which the iPhone 5S's A7 is much stronger at. Sure, 64 bit requires optimization too, but for most developers, that just means a recompile in Xcode instead of implementing the trouble more threading (and Android's threading APIs are not at all easy compared to iOS's.) So more likely in real world situations, with single core and dual core apps, you're going to see far better performance from the A7.
Google/LG do have a few things going in their favor. If they ever moved to 64 bit but kept the same 2.3 ghz frequency with quad cores, they'd have a monster on their hands. And with all their apps running under a virtual machine/JIT, they could recompile all their applications to run under 64 bit without the developer having to do anything at all.
But, on the other hand, there is nothing to stop Apple from building a larger device with a bigger battery and doing the exact same thing, and they're already done the hard part. Moving a chip to 64 bit is not easy, but adding a few extra cores and bumping up the clock speed is easy by comparison. And there have been constant rumors Apple is building a larger device. Apple could also forgo doubling their cores and upping their clock speed and just pocket the power savings. It might make them look bad in future benchmarks compared to "Hummer" phones, but if they could extend their battery life dramatically people might not care.
The NEON registers are 128-bits wide and there are 32 of them. If you have 32 bit data, you can process 128 chunks at a time!
I don't think you understand how SIMD is used. NEON instructions only apply to 1 register, so it only processes 4x 32 bit at a time.
Nexus 5 $350 no contract, direct from google:
https://play.google.com/store/devices/details/Nexus_5_16GB_Black?id=nexus_5_black_16gb&hl=en
iphone5s is $650
http://store.apple.com/us/buy-iphone/iphone5s
The only real comparison is to compare phone prices without contract, because on contract the additional cost of the phone is included in your bill which you pay over the term of the contract.
The N5 is so close to half price of the iphone5s as to make no difference. I used to grudgingly admit iphones could beat out androids back in the G1 days. The only thing apple has left these days is brand.
The NEON registers are 128-bits wide and there are 32 of them. If you have 32 bit data, you can process 128 chunks at a time!
I don't think you understand how SIMD is used. NEON instructions only apply to 1 register, so it only processes 4x 32 bit at a time.
You're right, I misspoke. The number of registers is great for pipelining and loading vectors of data, but you can only do an operation on one register at a time. Still a nice gain.
Can we put this in the "don't give a rats ass" category please.
Find a job you love, and never work a day in your life.
Stupid comparison. The earliest thing you listed happened over a hundred years ago. What GP is talking about was only a few years ago.
Perspective and context: try to gain some.
Everything except the laptop and the tape recorder, yes. Yes I did.
Well.. maybe. Or Maybe not. But Definitely not sort of.
Before 2011 I had a smartphone that did all that.
Before "smartphones" I regularly went out and about with a Key Map (the only way to get where you're going in Houston), a compass (one of them cheap suction cup ones that kept falling off), a mobile phone (a nokia "candy bar"), a cd player (with a tape adapter to plug into the car stereo) and a gameboy.
If I have been able to see further than others, it is because I bought a pair of binoculars.
New phone almost as fast as month old phone.
Xperia Z1 was released same day as iPhone 5s. It is faster, waterproof, and has higher res 1080 screen. It also has a 20.7MP camera with a much larger 1/2.3" sensor.
I thought you could get an app that makes the iPhone waterproof?
Yeah, here's the ad.
I am anarch of all I survey.
Yeah but that phone is half the price of the iPhone.
Pretty impressive to me.
It's because Google is dumping Nexus 5 with almost no profits in US market. Nexus 5 sold by LG in Taiwan market costs me almost twice.
I think you're talking about Android again... Media transcoding software wouldn't be allowed through the Apple app store, surely?
Wow, you're so far stuck up Google's ass, you can't see that Apple might actually be better from a developers perspective.
I'm also a developer, but a web app developer, and My God, Android was an outright nightmare...
We finished the iOS app _MONTHS_ before and launched it.
Android behaved exactly like IE6, it was a nightmare, the UI and app behaviour was a nightmare... after countless head-screaming meetings about why we couldn't launch for Android, and after pulling my hair out and fixing for one or two popular android handsets at the time... I resigned altogether.
To this day, they're only been able to make the app work for a small subset of Android devices - namely the popular S2/S3/and S4, along with one HTC device.
I'm now back to java web app development for desktops, but if I was to step back in the mobile world... there's no way I'm going near Android, in the same sense I don't go near IE6.
There's nothing stupid about it. I could have included the radio to TV transition as the primary media source if you want something more recent. Or perhaps the advent of cheap microwave ovens, or cable television vs. OTA broadcast. It's not my fault you were not able to grasp the point that new technology supersedes the old in many cases. It's called progress.