Except everything I said was true. Last year... let me make sure you got that... LAST YEAR it was a marketing gimmick.
Of course it was. There were no apps taking advantage of it in 2013!
I still have yet to find a game or any app that is in any manner noticeably different side-by-side on my 5S as my old 5. Show me one. It wasn't about 2013.
The genius idea is of course that they can sell devices with A7s for years to come, as they always have in the past with their other chips.
It was about the future. It's not say that the A7 isn't a significant step up and will provide Apple a solid foundation for years to come. It's not to say that it's performance can't be tapped to provide luscious visuals and massively more ram. But it wasn't last year.
None of this was logically unsound or "lies" so get over yourself bud.
And you have 1.2 million apps on your iPhone? Guess you make use of Search/Siri extensively.
And you have 1.2 million apps on your iPhone? Guess you make use of Search/Siri extensively.
Wow, is that how many apps there are now, that's difficult to wrap my head around, how does anybody find anything anymore. Let's see, I want a new music player, 90'000 hits, crap, okay that can play .wmv files, 68,000, wooo hoo, getting closer.
And you have 1.2 million apps on your iPhone? Guess you make use of Search/Siri extensively.
Wow, is that how many apps there are now, that's difficult to wrap my head around, how does anybody find anything anymore. Let's see, I want a new music player, 90'000 hits, crap, okay that can play .wmv files, 68,000, wooo hoo, getting closer.
As TS says: subcategories of subcategories of subcategories. I think iOS 8 is supposed to improve discovery; it's much too tricky finding anything now, isn't it?
Uh oh, this isn't sounding very good is it, I friggen hated Transmeta CPU's, they were ssssllloooowwww, I know, I had a Sony PictureBook. Will it be at least faster then the 32bit version, if not what's the point?
I can't say I owned anything Transmeta made but do recall the general dissatisfaction with the hardware. Everything I've read though indicates that this isn't exactly a one for one Transmeta port. The chip apparently fully executes ARM instructuons but the question that is unanswered is at one performance capability. Even though the cores are "wide" that doesn't mean much if instruction dispatch fail to keep all the slots filled. The fear here is that they have spent too much silicon on the code profiling and microcode caching hardware and have not optimized native ARM code execution. So you might have a chip that works great once it decides to cache the hot spots in the code and so so when running fresh ARM code.
This is of course speculation as no testable hardware has shipped yet. However history here is not good. Since this looks like a hybrid of Transmeta tech and normal ARM hardware ethos it will take some time to get a good handle of chip performance.
I fail to see how this will impact my Netflix viewing and Waze nav-ing experiences, on any device. This hardware race is a bit silly for 99% of actual device usage.
If you are a person with low expectations then hardware improvements will not be important to you. After all vegetables spend half their time in the dark.
However if you are the type of person that wonders why Safari is so damn slow or wonders why multitasking is so wanting then faster chips are very important to you. I actually wonder why you even read threads like this if you don't give a damn about hardware. To put it bluntly I'm not even sure how anybody can be happy with the state of today's handheld technology
You've got a fair point. If you represent the typical Android user, there's not much point in 64 bit if all you use is Netflix and Waze.
There isn't much point in his posting silly questions either. It really perplexes me that somebody that doesn't care about performance would post such a stupid question in this thread. A thread focused on a high performance processor.
Therein lies the quandary for Google. On the one hand, they are being forced out of the high-end by Apple, and have declared their focus on the low-end with Android L.
Pull away from the Android crowd and this chip looks to be far more interesting. Remember this is an NVidia product not a Google product. As such it has great potential outside of Android, here I'm thinking running straight Linux.
On the other hand, they are attempting a race to 64 bit and dominance in performance. It's all going to end up in a clusterfuck. Perhaps that's why you need two hands to operate Android phones...
You really need to get your head screwed on straight here, this is a NVidia product. I highly doubt they will tie success here to just Android.
If you are a person with low expectations then hardware improvements will not be important to you. After all vegetables spend half their time in the dark.
However if you are the type of person that wonders why Safari is so damn slow or wonders why multitasking is so wanting then faster chips are very important to you. I actually wonder why you even read threads like this if you don't give a damn about hardware. To put it bluntly I'm not even sure how anybody can be happy with the state of today's handheld technology
I choose not to live my life in frustration that the technology around the corner is going to solve everything for me, but no current technology will. Am I satisfied with the "state of today's handheld technology?" No, not in the sense that we would no longer need advances.
My point is that I'm they type of person who can make the most of existing technology, or even just what I have in my possession. Before I got a dovetailing jig, I made beautiful dovetailed drawers with hand tools. When I got started in my computer science studies, and could only afford a 2-generations-old computer, I learned not to expect fast compile times on large projects -- and wrote my code as carefully as necessary to minimize recompiles.
Most of my phone's on-time is spent in Netflix, Waze, or mail. There are times where I bang out more strenuous computing tasks, but in general, current technology is sufficient, even if it isn't inspiring.
For now, with my relatively slow Snapdragon S4 Pro, I still have a phone that silences itself between 9pm-6am if it's plugged in and face down. It still automatically toggles speaker phone with the proximity sensor, and it eliminates my passcode lock screen if I'm near familiar networks. These are great automated tasks that are hugely convenient, but don't take much processing. So the power flexibility makes up for a lot of the raw power shortfall -- because I'm sophisticated enough to learn how to script these features myself, making the most of the tools available, rather than spending time in dissatisfaction due to creeping expectations.
The chip apparently fully executes ARM instructions but the question that is unanswered is at one performance capability. Even though the cores are "wide" that doesn't mean much if instruction dispatch fail to keep all the slots filled.
David Kantar says that direct ARM instructions are 2-issue wide. So, on some code, it could be the same IPC as a Cortex-A8 or Cortex-A9. Ok, I joke.
The fear here is that they have spent too much silicon on the code profiling and microcode caching hardware and have not optimized native ARM code execution. So you might have a chip that works great once it decides to cache the hot spots in the code and so so when running fresh ARM code.
Yes. Great for multimedia, not so great for web browsing or productivity style applications.
Quote:
This is of course speculation as no testable hardware has shipped yet. However history here is not good. Since this looks like a hybrid of Transmeta tech and normal ARM hardware ethos it will take some time to get a good handle of chip performance.
I wouldn't be surprised if Nvidia has a lot of Transmeta folks and this is their 3rd crack at the architecture. Wait and see. Anyways, you can get the Hot Chips presentation here:
<span style="line-height:1.4em;">I actually do a fair bit of remote desktop, spreadsheets, docs, chrome, FB, and gmail. None of those are screaming for processor speed though. Neither are any of these:</span>
Android's so inefficient everything screams for processing power. Apparently half as much with the next release. Until they shift from half-native to true native that'll always be the case.
Android's so inefficient everything screams for processing power. Apparently half as much with the next release. Until they shift from half-native to true native that'll always be the case.
McD
Not sure what you're doing on Android, but my 4.4.4 N4 is pretty much idle all the time. Biggest spikes I see most days go up to 20%. I'll see 40% if I'm going crazy in Hawaii's valleys in Google Earth, but I can't keep it up that high for more than a couple seconds. Photosphere spikes for a second to 40% while stitching.
Android's so inefficient everything screams for processing power. Apparently half as much with the next release. Until they shift from half-native to true native that'll always be the case.
McD
First, no, Android is not inefficient as it could be but it's also not processor hungry either. Second, your talking about ART, which stands for Android Runtime, handles app execution in a fundamentally different way from Dalvik. The current runtime relies on a Just In Time Compiler to interpret bytecode, a generic version of the original application code. In a manner of speaking, apps are only partially compiled by developers, then the resulting code must go through an interpreter on a user's device each and every time it is run. The process involves a lot of overhead and isn't particularly efficient, but the mechanism makes it easy for apps to run on a variety of hardware and architectures. ART is set to change this process by pre-compiling that bytecode into machine language when apps are first installed, turning them into truly native apps. This process is called Ahead-Of-Time (AOT) compilation. By removing the need to spin up a new virtual machine or run interpreted code, startup times can be cut down immensely and ongoing execution will become faster, as well. So no, going half to full native, won't change anything, especially now that ART is in the picture, it's just as fast. I have been using Android 5 on my Nexus 5 for a while now and it's extremely quick. In fact, when a Sun Spider benchmark is performed I now get a score of 480, where previously I was getting a 720, the iPhone 5s has a score of 415 for comparison.
Remember this is an NVidia product not a Google product. As such it has great potential outside of Android, here I'm thinking running straight Linux.
Same here, you should really think about grabbing one of these for 192.00. Even if your not much of a tinkerer, it still makes for a great mini Linux computer.
Comments
Completely and utterly false. Enjoy your lies.
Utterly incorrect in every conceivable way.
And you have 1.2 million apps on your iPhone? Guess you make use of Search/Siri extensively.
Wow, is that how many apps there are now, that's difficult to wrap my head around, how does anybody find anything anymore. Let's see, I want a new music player, 90'000 hits, crap, okay that can play .wmv files, 68,000, wooo hoo, getting closer.
As TS says: subcategories of subcategories of subcategories. I think iOS 8 is supposed to improve discovery; it's much too tricky finding anything now, isn't it?
I can't say I owned anything Transmeta made but do recall the general dissatisfaction with the hardware. Everything I've read though indicates that this isn't exactly a one for one Transmeta port. The chip apparently fully executes ARM instructuons but the question that is unanswered is at one performance capability. Even though the cores are "wide" that doesn't mean much if instruction dispatch fail to keep all the slots filled. The fear here is that they have spent too much silicon on the code profiling and microcode caching hardware and have not optimized native ARM code execution. So you might have a chip that works great once it decides to cache the hot spots in the code and so so when running fresh ARM code.
This is of course speculation as no testable hardware has shipped yet. However history here is not good. Since this looks like a hybrid of Transmeta tech and normal ARM hardware ethos it will take some time to get a good handle of chip performance.
If you are a person with low expectations then hardware improvements will not be important to you. After all vegetables spend half their time in the dark.
However if you are the type of person that wonders why Safari is so damn slow or wonders why multitasking is so wanting then faster chips are very important to you. I actually wonder why you even read threads like this if you don't give a damn about hardware. To put it bluntly I'm not even sure how anybody can be happy with the state of today's handheld technology
You really need to get your head screwed on straight here, this is a NVidia product. I highly doubt they will tie success here to just Android.
If you are a person with low expectations then hardware improvements will not be important to you. After all vegetables spend half their time in the dark.
However if you are the type of person that wonders why Safari is so damn slow or wonders why multitasking is so wanting then faster chips are very important to you. I actually wonder why you even read threads like this if you don't give a damn about hardware. To put it bluntly I'm not even sure how anybody can be happy with the state of today's handheld technology
I choose not to live my life in frustration that the technology around the corner is going to solve everything for me, but no current technology will. Am I satisfied with the "state of today's handheld technology?" No, not in the sense that we would no longer need advances.
My point is that I'm they type of person who can make the most of existing technology, or even just what I have in my possession. Before I got a dovetailing jig, I made beautiful dovetailed drawers with hand tools. When I got started in my computer science studies, and could only afford a 2-generations-old computer, I learned not to expect fast compile times on large projects -- and wrote my code as carefully as necessary to minimize recompiles.
Most of my phone's on-time is spent in Netflix, Waze, or mail. There are times where I bang out more strenuous computing tasks, but in general, current technology is sufficient, even if it isn't inspiring.
For now, with my relatively slow Snapdragon S4 Pro, I still have a phone that silences itself between 9pm-6am if it's plugged in and face down. It still automatically toggles speaker phone with the proximity sensor, and it eliminates my passcode lock screen if I'm near familiar networks. These are great automated tasks that are hugely convenient, but don't take much processing. So the power flexibility makes up for a lot of the raw power shortfall -- because I'm sophisticated enough to learn how to script these features myself, making the most of the tools available, rather than spending time in dissatisfaction due to creeping expectations.
The chip apparently fully executes ARM instructions but the question that is unanswered is at one performance capability. Even though the cores are "wide" that doesn't mean much if instruction dispatch fail to keep all the slots filled.
David Kantar says that direct ARM instructions are 2-issue wide. So, on some code, it could be the same IPC as a Cortex-A8 or Cortex-A9. Ok, I joke.
Yes. Great for multimedia, not so great for web browsing or productivity style applications.
I wouldn't be surprised if Nvidia has a lot of Transmeta folks and this is their 3rd crack at the architecture. Wait and see. Anyways, you can get the Hot Chips presentation here:
http://www.setphaserstostun.org/hc26/HC26-11-day1-epub/HC26.11-2-Mobile-Processors-epub/
Gratefully posted by some folks from realworldtech.
Android's so inefficient everything screams for processing power. Apparently half as much with the next release. Until they shift from half-native to true native that'll always be the case.
McD
Android's so inefficient everything screams for processing power. Apparently half as much with the next release. Until they shift from half-native to true native that'll always be the case.
McD
Not sure what you're doing on Android, but my 4.4.4 N4 is pretty much idle all the time. Biggest spikes I see most days go up to 20%. I'll see 40% if I'm going crazy in Hawaii's valleys in Google Earth, but I can't keep it up that high for more than a couple seconds. Photosphere spikes for a second to 40% while stitching.
Android's so inefficient everything screams for processing power. Apparently half as much with the next release. Until they shift from half-native to true native that'll always be the case.
McD
First, no, Android is not inefficient as it could be but it's also not processor hungry either. Second, your talking about ART, which stands for Android Runtime, handles app execution in a fundamentally different way from Dalvik. The current runtime relies on a Just In Time Compiler to interpret bytecode, a generic version of the original application code. In a manner of speaking, apps are only partially compiled by developers, then the resulting code must go through an interpreter on a user's device each and every time it is run. The process involves a lot of overhead and isn't particularly efficient, but the mechanism makes it easy for apps to run on a variety of hardware and architectures. ART is set to change this process by pre-compiling that bytecode into machine language when apps are first installed, turning them into truly native apps. This process is called Ahead-Of-Time (AOT) compilation. By removing the need to spin up a new virtual machine or run interpreted code, startup times can be cut down immensely and ongoing execution will become faster, as well. So no, going half to full native, won't change anything, especially now that ART is in the picture, it's just as fast. I have been using Android 5 on my Nexus 5 for a while now and it's extremely quick. In fact, when a Sun Spider benchmark is performed I now get a score of 480, where previously I was getting a 720, the iPhone 5s has a score of 415 for comparison.
Remember this is an NVidia product not a Google product. As such it has great potential outside of Android, here I'm thinking running straight Linux.
Same here, you should really think about grabbing one of these for 192.00. Even if your not much of a tinkerer, it still makes for a great mini Linux computer.
Jetson TK1 Development Kit