nVidia is targeting Windows, too: Windows RT.
And Chrome is much faster in Kraken than IE10. So i think it's fair.
BTW: 1,4GHz Jaguar gets 480ms in Sunspider with IE10. Tegra 4 500ms with Android. And IE10 is much better than anything on Android.
if you think ARM A15 is as fast as Jaguar you are thoroughly mistaken. the A6-1450's single core clock is 1.4 Ghz. for every extra thread clocks drop 100 - 200 mhz. dual thread seems to be 1.3 ghz. quad core seems to be 1 - 1.1 ghz.
as for performance
http://www.anandtech.com/show/6974/amd-kabini-review/3
"Here we see a 14% improvement over Bobcat, likely closer to 20% if we normalized clock speed between the partstracking perfectly with AMD's promised IPC gains for Jaguar.
Jaguar seems to be around 9-20% faster than Bobcat depending on the benchmark. Multithreaded workloads are obviously much better as there are simply more cores to run on. In practice, using the Kabini test system vs. an old Brazos machine delivers a noticeable difference in user experience. Clover Trail feels anemic by comparison and even Brazos feels quite dated.
Seeing as how Bobcat was already quicker than ARM's Cortex A15, its no surprise that Jaguar is as well "
you can see from the relation between A4-5000 and E-350 that Kraken does not exploit 4 cores. so its a good measure of single/dual thread performance. the Samsung ARM A15 at 1.7 Ghz gets decimated by Jaguar 1.5 Ghz. remember Temash will turbo to 1.4 Ghz for single thread and should not be far behind A4-5000. Even for dual thread it should be just 200 Mhz slower than A4-5000.
Tegra 4 will draw less power but will not stand a chance against Temash in raw performance.