In trying to accomodate desktops, Metro fails as a well-designed tablet UI. In trying to accomodate tablets, Metro fails as a desktop UI.
http://www.useit.com/alertbox/windows-8.html
And on Windows Server 2013, it's even worse!
http://semiaccurate.com/2012/09/12/m...-the-bleeding/
Cheezburger documents:
http://www.useit.com/alertbox/windows-8.html
As mentioned in the introduction, Windows 8 encompasses two UI styles within one product. Windows 8 on mobile devices and tablets is akin to Dr. Jekyll: a tortured soul hoping for redemption. On a regular PC, Windows 8 is Mr. Hyde: a monster that terrorizes poor office workers and strangles their productivity.
The situation is much worse on regular PCs, particularly for knowledge workers doing productivity tasks in the office. This used to be Microsoft's core audience, and it has now thrown the old customer base under the bus by designing an operating system that removes a powerful PC's benefits in order to work better on smaller devices.
The underlying problem is the idea of recycling a single software UI for two very different classes of hardware devices. It would have been much better to have two different designs: one for mobile and tablets, and one for the PC.
I understand why Microsoft likes the marketing message of "One Windows, Everywhere." But this strategy is wrong for users.
The situation is much worse on regular PCs, particularly for knowledge workers doing productivity tasks in the office. This used to be Microsoft's core audience, and it has now thrown the old customer base under the bus by designing an operating system that removes a powerful PC's benefits in order to work better on smaller devices.
The underlying problem is the idea of recycling a single software UI for two very different classes of hardware devices. It would have been much better to have two different designs: one for mobile and tablets, and one for the PC.
I understand why Microsoft likes the marketing message of "One Windows, Everywhere." But this strategy is wrong for users.
http://semiaccurate.com/2012/09/12/m...-the-bleeding/
Servers are about management, efficiency, low overhead control, and remote management. Command lines rule, remote accessibility is mandatory, and anything that gets in the way is a bad idea. Microsoft is bleeding marketshare at alarming rates, so how do you stop it? Big colorful graphics that make remote management slow, tie it to Microsoft end user devices, and a UI that is painful to work with if you don’t have a touch screen. Right now, Windows Phone is 2% of the market and screens are unwelcome in server rooms. Touch screens do not exist in server rooms at all. What genius thought tying these two things in to a wounded product line would help?
To make matters even better, the UI and control schemes that people are familiar with are gone. In its place is a UI that is familiar to no one, makes users hunt for tools that used to be second nature, and requires a mouse, touch screen, and Windows Phone 8 to remotely manage. What percentage of tech gurus use Windows Phone 8 again? Please note, Windows Phone 7.x won’t cut it here, it has to be 8. And those 3rd party tools you used to use to manage things? Gone too.
To make matters even better, the UI and control schemes that people are familiar with are gone. In its place is a UI that is familiar to no one, makes users hunt for tools that used to be second nature, and requires a mouse, touch screen, and Windows Phone 8 to remotely manage. What percentage of tech gurus use Windows Phone 8 again? Please note, Windows Phone 7.x won’t cut it here, it has to be 8. And those 3rd party tools you used to use to manage things? Gone too.
)
It was also quite buggy. Most of that has been fixed since about KDE 4.5, but the early days were underwhelming.
Comment