Linked by Thom Holwerda on Fri 30th Nov 2012 21:54 UTC
Permalink for comment 543840
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-07-06
... which would mean that touchscreen laptops suck. I will assume that until Anand does a proper review ...
I second that - the only thing that is probably worse than the articles are the forums themselves. The reality is that touch screens make sense for devices like the ThinkPad Yoga but honestly the attraction beyond a few niches is pretty much a novelty that is later ignored just as Thunderbolt on my old iMac pretty much stood idle as I felt high and mighty believing I had something that none of the PC users had. The reality is that when the rubber hit the road you'll see those touch desktop screens will be in use for a while and then the end user will go back to using a mouse/keyboard just the same with traditional laptops.
If the aim of Metro was to spur on the development of hybrid devices then hey, that is great, cool bananas but if they're trying to get touch screens in all devices no matter how stupid and impractical then such a feature for many users will become as useless as the Thunderbolt port I had on my iMac. If Microsoft really want to do something that'll benefit end users then they should expand WinRT so then not only Metro applications are written in it but also desktop ones to - have context sensitive XAML interfaces where the application launches either in tablet or desktop mode depending upon what mode it is being run in at that point in time. Having an improved and evolved API would also help developers as well as to avoid the esoteric issues of win32 and move over to a cleaner set of API's so then more focus can be paid to the applications than working around issues or Microsoft having to balance moving forward and maintaining backwards compatibility. IMHO it seems that the touch screen is to Microsoft like what Retina is to Apple - a gimmick to bring in the punters but closer inspection show very little benefit to end users in day to day real world usage.