NVIDIA's Tegra 3 Outruns Apple's A5 In First Benchmarks 390
MojoKid writes "NVIDIA's new Tegra 3 SoC (System on a Chip) has recently been released for performance reviews in the Asus Eee Pad Transformer Prime Android tablet. Tegra 3 is comprised of a quad-core primary CPU complex with a 5th companion core for lower-end processing requirements and power management. The chip can scale up to 1.4GHz on a single core and 1.3GHz on up to four of its cores, while the companion core operates at 500MHz. It makes for a fairly impressive new tablet platform and offers performance that bests Apple's A5 dual-core processor in more than a few tests. The Asus Eee Pad Transformer Prime with optional keyboard dock and NVIDIA's Tegra 3 is set to be available in volume sometime around December 19th."
Re:Thank you Captain Obvious (Score:5, Interesting)
If anything, the news is that the iPad2 actually *wins* in half of the linked benchmarks.
Performance is one important attribute... (Score:4, Interesting)
Re:You know why Apple's winning? It's not about sp (Score:2, Interesting)
No offense, but Apple's got marketing ... the experience side I've experienced is different.
Nearly every person who sees my wife using her new Motorola Droid3 or me using my Dell Streak 5 ask which IPhone we have (lol). Then we show them our customized home screens with information instantly visible, from calendar appointments (I use S2 calendar widgets) to recent friend updates to weather forecasts. Then she slides out the very nice keyboard on hers, or more likely demonstrates how fast it is to enter text with Swype or voice on Android, and how you can instantly jump between recently used apps that are still running in the background, and they're sold.
I haven't met a single IPhone user who says "oh my phone can do that better" yet. The only thing I've heard in favour of an IPhone from its users is "it makes me feel good."
Re:You know why Apple's winning? It's not about sp (Score:4, Interesting)
I work for a company that does marketing for both Apple and Android manufacturers. Trust me, they all have great marketing teams and big budgets. The success of the products isn't as simple as marketing.
The difference is that Apple takes the time to do both hardware AND software specifically so that they can build a unified consistent experience. Whereas Android manufacturers just slap the Android OS on the hardware and hope for the best.
To counter your anecdotes, time and time again I hear people bitching about their Android devices because it's slow, or software is buggy and inconsistent, or UI is confusing, etc. I think it's pretty telling that the "touch" event in the Android API is called "click".
Re:You know why Apple's winning? It's not about sp (Score:4, Interesting)
http://news.cnet.com/8301-30685_3-57321157-264/adobe-abandons-flash-plug-in-for-mobile-devices-report/ [cnet.com]
No, you make one app with resources for both. Developers choose to separate apps.
http://support.apple.com/kb/ht1288 [apple.com]
Strangely that doesn't seem like a solution for my car or gym equipment,,,,,
Re:You know why Apple's winning? It's not about sp (Score:3, Interesting)
I'm talking about consumers, you are talking about developers. That is apples and oranges, though personally, from my experience with Android, I personally disagree. I would ask, have you designed any apps in Android and then tried to port them to iOS? The design pattern for Android and iOS is inherently incompatible so I would expect a port in either direction to be complicated and take longer than the original effort since you are trying to replicate functionality that is not done the same way. I will admit that I have not been working with iOS as long as you, but I find it extremely obtuse to develop on as it requires a completely different way of thinking about things. (Also, I hate xcode with a burning passion, but that's beside the point.)
I would hazard that a lot of people's experiences impact how they perceive starting development in mobile too. I came from a MSVC++, MSVC# background with lots of .Net and started mobile development on Windows Mobile. I found Android a far simpler transition to make where as I found the documentation for iOS completely unhelpful and the bastardized visual approach to some of the development that couldn't easily be replicated in code to be convoluted and confusing in xcode (not to mention major stability problems. It was crashing on me daily until I switched to Monotouch to avoid using it any more than necessary.