Quote:
For business and enterprise installations, where the upgrade cost — both in terms of time and money — is higher, I am more ambivalent. That the Metro interface cannot be disabled by system administrators is troubling. By installing Windows 8, companies will implicitly force its employees to use a new interface that could severely dent productivity. This issue is compounded by the fact that almost all of Windows 8 Desktop’s new features are oriented towards at-home consumers, rather than office workers. I think Windows 8 will be a very tough sell in the enterprise.
http://www.extremetech.com/computing/138177-under-the-hood-of-windows-8-or-why-desktop-users-should-upgrade-from-windows-7/3
It's not so much the start screen, it's the way Metro Apps also maximize and all.
edit: also developers take a gamble coding for it (the Metro UI side, not the desktop side)
http://www.techrepublic.com/blog/10things/10-reasons-windows-8-will-be-painful-for-developers/2885
Quote:
1: Market reboot
If you want your applications to be fully compatible with Windows 8 (including running on ARM CPUs), you’ll need to do a full rewrite in Windows 8/WinRT. This may be great for developers looking to break into markets with established players. But if you are the established player, you are suddenly back at square one.
2: The asynchronous model
Windows 8 development is highly dependent upon asynchronous operations for anything that is long running. While that may be a cute trick in some scenarios, it is downright frustrating in others (like trying to download a file). It isn’t just the work needed to handle the async call; it’s things like error handling and reporting problems back to the user. It requires a whole new approach to the UI from what developers (especially WinForms developers) are used to.
3: Lack of direct disk access
Windows 8 cuts off direct access to the system in quite a few ways, but the one that will hurt typical developers the most is the lack of disk access. Windows 8 follows an extreme isolation model for applications, and if your application requires access to data outside its own confined little world (including networked services you can access), you can forget about porting it to Windows 8.
4: Touch UI paradigm
Unless you have been writing a lot of mobile apps, shifting to the new UI style, which is designed for touch interaction, is going to pretty tough. It took me a long time to get a feel for what works well and what doesn’t. To make things more difficult, what looks and works well on a screen using a mouse and keyboard can be a poor experience with touch, and things that work well with touch often are a struggle to use on the screen. It’s a tricky balancing act, and as the uproar over the new UI in Windows 8 shows, even Microsoft is struggling to get it right despite having had a few years of experience with it.
...
10: The trail of dead tech
This is the one that really breaks my heart. Microsoft has a history of pushing a technology as “the next big thing” and then leaving it dying on the vine a few years later. We don’t know if Microsoft will back off its Windows 8 strategy before launch, right after launch (Kin), or a few years down the road (Zune, Silverlight). If the new Windows 8 paradigm is not a success, Microsoft may very well change course in a way that renders all your hard work on Windows 8 native applications a waste of time.
Maybe it'd be different if you had a 1080p touchscreen?
They're about $300 for 2 point touchscreens (optical)...
http://www.newegg.com/Product/Product.aspx?Item=N82E16824116464
$280 for Planar
http://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=5716147&CatId=1449
and $500+ for true multitouch
http://www.neowin.net/news/two-new-windows-8-certified-touchscreen-monitors-from-acer
http://www.newegg.com/Product/Product.aspx?Item=N82E16824176060&name=Touchscreen-Monitors
http://configure.us.dell.com/dellstore/config.aspx?c=us&cs=19&l=en&oc=S2340TSAP&s=dhsEdited by AlphaC - 10/25/12 at 5:51pm