How does it perform versus the A14.. is it faster, more power efficient? Qualcomm has always been about 20% slower than Apple. It must be true this time too, because they haven't said it's faster.. they have not touted it.. so the answer is must be no it's not (unless they have a braindead marketing department).
How does it perform versus the A14.. is it faster, more power efficient? Qualcomm has always been about 20% slower than Apple. It must be true this time too, because they haven't said it's faster.. they have not touted it.. so the answer is must be no it's not (unless they have a braindead marketing department).
Well, if it is still a 32 bit processor, I can't imagine it will be faster than Apple's line of 64 bit SoCs.
And as far as power efficiency: Why do you think Android phones have twice the battery capacity of Apple phones, yet still get nearly identical run times?
I doubt this is some revolutionary advancement in Qualcomm's offerings. Their real expertise lies in radios, not CPUs.
The battery life thing isn't merely a matter of the SoC—Apple has better integration, fewer screen pixels and less RAM. Those last two are reasonable trade-offs, given that most people can't tell the difference at a normal viewing distance for the screen, and more RAM doesn't really help unless you want to keep a lot of web pages in memory or you're swapping between apps a lot. Android's flexibility incurs a cost.
I write large games. For a living. That's not really what we're talking about. (Even then, most code that I write isn't RAM limited; textures and models take up way more than my engine code ever will. I have to be more mindful of HOW I allocate RAM than how much.)
On A PHONE, RAM isn't the biggest consideration. 4GB of RAM is perfectly workable. You're not multitasking so much that you need to be able to keep 10 apps in memory at once, and I doubt most apps even get close to using all 4GB of RAM at a time. I
Ah, but now that convergence is happening, it is more important than ever how much RAM/CPU/GPU is in a phone, and how much is being consumed by OS tasks.
I am a bit disappointed with the Librem5 specs, I'm hoping they release an updated model with more ram/CPU grunt in a year or two.
"Nuclear war would really set back cable."
- Ted Turner
versus Apple A14 ? (Score:0)
How does it perform versus the A14 .. is it faster, more power efficient? Qualcomm has always been about 20% slower than Apple. It must be true this time too, because they haven't said it's faster .. they have not touted it.. so the answer is must be no it's not (unless they have a braindead marketing department).
Re: (Score:2, Interesting)
How does it perform versus the A14 .. is it faster, more power efficient? Qualcomm has always been about 20% slower than Apple. It must be true this time too, because they haven't said it's faster .. they have not touted it.. so the answer is must be no it's not (unless they have a braindead marketing department).
Well, if it is still a 32 bit processor, I can't imagine it will be faster than Apple's line of 64 bit SoCs.
And as far as power efficiency: Why do you think Android phones have twice the battery capacity of Apple phones, yet still get nearly identical run times?
I doubt this is some revolutionary advancement in Qualcomm's offerings. Their real expertise lies in radios, not CPUs.
Re: (Score:2)
The battery life thing isn't merely a matter of the SoC—Apple has better integration, fewer screen pixels and less RAM. Those last two are reasonable trade-offs, given that most people can't tell the difference at a normal viewing distance for the screen, and more RAM doesn't really help unless you want to keep a lot of web pages in memory or you're swapping between apps a lot. Android's flexibility incurs a cost.
RAM does not help (Score:2)
My god...RAM does help are you serious in any suggestion that it doesn't.
Go back to school. Hell watch a five minute YouTube video.
I mean it learn to code write a small game.
Re: (Score:2)
I write large games. For a living. That's not really what we're talking about. (Even then, most code that I write isn't RAM limited; textures and models take up way more than my engine code ever will. I have to be more mindful of HOW I allocate RAM than how much.)
On A PHONE, RAM isn't the biggest consideration. 4GB of RAM is perfectly workable. You're not multitasking so much that you need to be able to keep 10 apps in memory at once, and I doubt most apps even get close to using all 4GB of RAM at a time. I
Re: (Score:2)