Linked by Thom Holwerda on Wed 6th Mar 2013 19:00 UTC
Microsoft One of the major lacking features in the newest Office: no Metro applications. In fact, the only reason Windows RT has a desktop at all is because the Office team was unable to create Metro applications in time for the release of Windows RT. I often thought this was a classic case of two important divisions within Microsoft not getting along and not being aligned, but now that I have my own Surface RT, I'm starting to realise that there's a far simpler, and thus more likely, explanation: Metro is simply not ready for anything serious - or for anything at all, really.
Thread beginning with comment 554406
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Comment by BeamishBoy
by Nelson on Wed 6th Mar 2013 23:09 UTC in reply to "RE: Comment by BeamishBoy"
Member since:

Also worth noting , the Tegra 3 inside the Surface RT doesn't take advantage of 4 PLUS 1 architecture for distributing work across five cores.

Its not as optimized as other ARM SoCs on Windows RT, also clocked lower overall. A major miss by Microsoft.

Reply Parent Score: 3

tylerdurden Member since:

Yeah, Windows RT apparently does not support the low power 5th core in the Tegra3. Which is why they used the lower clock frequency to reduce overall power consumption. Basically MS used a brute force HW approach to deal with the shortcomings of their own OS scheduler. I assume Microsoft had to get something out of the door pronto, before the iPad or Android get entrenched further.

Edited 2013-03-07 04:49 UTC

Reply Parent Score: 4

RE[4]: Comment by BeamishBoy
by Nelson on Thu 7th Mar 2013 04:45 in reply to "RE[3]: Comment by BeamishBoy"
Nelson Member since:

Correct, and I meant in a more generalized fashion. Its the auxiliary core. This gives the Surface RT less battery life out of the gate, which then requires the underclocking which in turn causes the performance issues.

Reply Parent Score: 3