Slashdot Mirror
Can Microsoft Afford To Lose With Windows 8?
snydeq writes with the opinion that Microsoft can afford Windows 8 failing on the desktop. From the article: "Windows 8 is an experiment that may well fail, but Microsoft will cull invaluable feedback for Windows 9 in the process, long before Windows 7 runs out of gas, writes InfoWorld's Serdar Yegulalp. 'Can Microsoft really afford to alienate one of its biggest market segments for a whole product cycle? In a word: Yes. In fact, doing something this risky might well be vital to Microsoft's survival,' Yegulalp writes. 'Microsoft needs to gamble, and right now might well be the best time for the company to do it. The company needs to learn from its mistakes as quickly and nimbly as they can — and then turn around and make Windows 9 exceed all of our expectations.'"
Microsoft has managed to weather several OS flops (Windows Me anyone?) thanks to their domination of the market, but with Android gadgets and iPhones becoming pervasive can they pull it off again?
Don't forget Windows 2000, which many preferred over XP because of its stability and lack of bells and whistles bogging it down.
It may not have been a big consumer hit, because there never were any cheaper "home" versions. But it was a big hit for businesses and power users.
Nor NT4, which was a workhorse for a long time.
I'd include Windows 3.11 too, which, crappy as it was, didn't have the stability problems of 95, and was thus used well beyond its EOL.
I figured that I'd just do what I did with Vista, and run the server edition of Windows 8 instead of the consumer edition, so that I can have all the new capabilities without the tablet UI.
No such luck.
I ran up the beta and got a few things up and running on it, and it's just mind-blowing to experience how horrendously unusable it is first hand. This is the server edition, mind you, and it had animations, things sliding around, the start menu is gone, and some notification popped up that said something like "tap here to view details". Tap? On a server? Are you kidding me? Everything is a tablet now?
The strangest thing is that the PowerShell 3 command line is so fantastically good* that I almost don't care that they've fucked up the GUI, but for most people any improvements are going to be swamped by the atrocious user interface.
They've stuffed up everything. Things like the new Server Manager look pretty, but it does odd things like adding new menu items after a delay. After clicking some item like a server role, at first maybe only three or four menu items would be shown, so you think, ah well, nothing I can do here... and then after two seconds more menu items appear out of nowhere. If you're like me and click fast, you can miss critical things because some idiot decided to lather on the WinRT asynchronous APIs without any thought to the impact on usability. It's one thing if a placeholder changes after a delay, but to keep structure hidden until an arbitrary delay is a huge design flaw. And why the fuck is it asynchronous in the first place, anyway? Why aren't menu items known ahead of time, like you know... in all other software ever made by man?
Everything has cute tiles now, none of which are big enough to show their text content, so you find yourself having to choose between "Active Direct...", "Active Direct...", or "Active Direct...". It doesn't help that the icons are all cool and Metro and lack distinguishing characteristics.
I love the nested scrollbars, where the horizontal and vertical scrollbars are attached to two different controls with different sizes, where one of them can be used to scroll the other scrollbar into an invisible location.
Of course, everybody has covered the idiocy of Microsoft deciding to eliminate the Start menu, but on Windows Server it's particularly bad because there's a vaguely similar looking icon in its place! If you don't click exactly in the corner of the screen, you launch Server Manager instead, which is not a lightweight app, and can take a while to launch even on an SSD. Expect to learn quickly from your mistakes, because you'll be punished for making them. A lot.
I still haven't figured out how to quickly get a list of all start menu items, without first searching for something and then erasing the search term so that everything matches. I'm sure there's a better way, but it's not obvious to me.
Some of these things might be a bit nitpicky, but from what I've seen the flaws are pervasive, and it's a bad sign that even the most commonly used GUI screens have glaring usability problems despite having what appears to be final layout and artwork.
It's one thing to grumble and have to get used to something new and different if it's better, but it's a whole different story when I'm forced to get used to something that is not only objectively worse, but also totally inappropriate for the type of product: "tap here" on Windows Server Datacenter Edition tells you everything you need to know about Microsoft's myopic vision.
*) While they've added some impressive features to PowerShell 3, they've fixed none of the bugs. For example, (Get-ADUser "invalidusername" -EA SilentlyContinue) still throws an exception even though it was told to fail silently. This bug affects a lot of different things and was reported to Microsoft back when PowerShell 2 was still beta! I'm going to whip my crystal ball out and predict that this bug will not get fixed until, lets say, PowerShell 5 Service Pack 2, at which point nobody will care because we'll all be using Apple computers and Google cloud services instead.