Linked by Yoni on Fri 18th Jan 2013 21:56 UTC
Permalink for comment 549497
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
Linked by Thom Holwerda on 04/16/13 9:29 UTC
Linked by Thom Holwerda on 04/15/13 22:44 UTC
More Features »
Sponsored Links



Member since:
2005-06-29
That's been almost exactly my experience with it, and I've mastered some of the most esoteric and backwards interfaces out there under GNU/Linux and other OSes. I got the basics of navigating Metro and the slightly tweaked classic desktop, but anything beyond web browsing seems to be purposely hidden. Using a keyboard and mouse in Metro feels like using a Nintendo WiiMote to navigate Windows 7: Inaccurate, slow, painful, and confusing.
And I get what Microsoft is trying to do, but they are trying too hard and too soon. I realized something else about Metro: It's almost as if it's designed to eventually work with a Kinect device for input. A lot of the touch-friendly gestures would work well with such a device, to the point that I wonder if they actually used it during development (in parallel to the version of Metro that's on the Xbox 360).
Of course, as far as I know the Kinect isn't fully supported on Windows 8 yet; RT doesn't support it at all and there are only basic drivers for 8. Perhaps they realized what kind of monstrosity they had built and scrapped those plans, assuming they even had them to start with. I guess we'll never know.