Slashdot Mirror
The Windows 8 Power Struggle: Metro Vs Desktop
MojoKid writes "Metro, Microsoft's new UI, is bold; a dramatic departure from anything the company has previously done in the desktop/laptop space, and absolutely great. It's tangible proof that Redmond really can design and build its own unique products and experiences. However, the transition to Metro's Start menu is jarring for some desktop users, and worse yet, Desktop mode and Metro don't mesh well at all. The best strategy Microsoft could take would be to introduce users to Metro via its included apps and through tablets, while prominently offering the option to maintain the Desktop environment. Power users who choose to use the classic UI for desktops and laptops can still be exposed to Metro via tablets and applications without being forced to wade through it on their way to do something important."
Let's see; I work on two 22 inch monitors. I can move from the far left edge to the far right edge with a three inch movement of my mouse. Now you want me to have to lean toward the monitors and move my arm over three feet to accomplish the same thing. How ergonomic! How NEW! How efficient!
You've missed the point. Why do Microsoft believe that people want or need touch monitors? Why do Microsoft believe large-dimension touch interfaces are better interface than a mouse?
Syllable : It's an Operating System
It's interesting how the comments on Apple/iPad/Post-PC articles, financials of Apple/Dell/HP etc. state that "MS is dying in the Post-PC" era, but now when they come out with a solution to make a OS run on different form factors and to have tablets that are not just consumption devices, ...
Tablets don't have to be just for consumption - people are already using iPads and the like for creative purposes. But, when you think about it, most of what the typical person uses even a full-blown computer for tends to be mainly consumption and communication - Netflix, YouTube, Facebook, email, chat, etc. Even for work, the most content creation they do involves making a Word document or an Excel spreadsheet.
As far as that "vast Win32 ecosystem" goes... remember that Windows tablets aren't exactly a new idea. Microsoft has tried - and failed - to leverage that vast ecosystem to make Windows-based phones and tablets a success before. Time will tell regarding Metro, of course; but while you seem to think their success is a foregone conclusion, recent history shows otherwise. It comes down to whether or not Microsoft learned from their previous failures, which is something I, for one, am not convinced of.
#DeleteChrome
I don't agree with Thurrot's analysis that "the desktop is just an app." Oh really? The desktop is still there, with Explorer, the taskbar, the system tray, and every other feature the desktop has ever had, and Thurrot wants us to believe this is somehow just some little "app" that's running inside of Metro? Hardly. The desktop is still the desktop. It is Windows.
What Windows 8 has done is given us this new launcher application, called Metro, which accepts plug-ins, called apps, and which will now launch automatically when you login to the system and again every time you push the Start button. Metro feels like the ultimate terminate-and-stay-resident program from the 80s, where every time you push the hotkey it takes over your entire screen.
Also, try to spend a few minutes learning shortcuts etc. before dissing the experience. It's not a SP for Windows 7, it's a new OS.
No, it isn't. It really isn't. Keyboard shortcuts do not make an "OS." The fact that the device drivers for every weird hardware device on my laptops carried over from Windows 7 to Windows 8 without a hitch demonstrates that the two are essentially the same OS.
What Microsoft has done with Windows 8 is it has taken a UI that works and put a big curtain in front of it (Metro) so that every time you want to use the OS the way you're accustomed to doing, you have to push the curtain aside. And as soon as you push the wrong button (the Windows key) or you want to launch a new application, the curtain drops down again.
They envision that with Windows 8, most new monitors will be touch enabled because of the demand so that for some functions(like clicking on links), people can use touch.
Just because I can use touch doesn't mean I will want to. I am not going to be reaching across my desk to click on links when there's a mouse sitting in my right hand. I don't need a new repeat strain injury and I don't want to smear my monitor with fingerprints. Poking around in midair with your fingers looks cool in movies, but in practice what we do now is more efficient, which makes it preferable. It's not logical to get rid of the more efficient way of doing things for the sake of something that looks cool.
You may disagree with the vision, but you can't disagree that there is a method behind the madness.
I don't disagree that there's a method. But that doesn't mean it's not madness. When your friend guns his engine and says, "Don't worry, I know what I'm doing -- we can make it across the canyon," it's time to get out of the car.
Breakfast served all day!
I hate to say this--but this concept of 'Apps' that everybody is latching on to--it is a huge pile of steaming buzzword. Yes their are applications, but the concept that all of computing can be neatly tucked and packed into an easily marketable single purpose flashy shiny big round button GUI software as a service plug in API model full of synergism and one-click-wonder wow--perhaps, but not for the power users, not for enterprise. There may be a day, but it isn't this decade IMO. I understand how consumers want this and blah blah rah grandma simplicity blah new age computing blah ease of use apple blah, but I'm here to comment about Apps and how I hear that word used in the wrong places (IMO).
Where's my 'app' for DBA activity? Where's my simple one click 'app' that monitors hundreds of servers, routers, switches? Where's my 'app' that automates my build processes? Where's my app that gives my complex analysis of all my interconnected nodes? You wont find them--not soon and not on 'markets'. Because these are complex intertwined multi-APPLICATION, to use the full word, work-flows that require desktops or complex usage of scripting and consoles. Sorry but for power use, it's just the way it is, in this decade and probably a few to come. These things can be done well and simply, but not without serious power-tools and planning.
Let's me honest, computing has been around for decades now, and even though on the consumer level 'apps' reign supreme it seems, there will always always always be power users who will need more complex environments for the vast array of software suites, tools, languages, and utilities needed to maintain and administer complex networks for build processes or whatever. Perhaps there will be a day when it is all unified. But that would require vast cooperation across industries, standards bodies, companies, open-sources houses, etc. Until some defacto design standard from layer 1 to 7 and from user space to kernals to whatever is implemented across the industry, nothing will ever be 'simple apps' while separate unique tools and such exist--thus guaranteeing the lifetime of the terminal and the desktop. It seems we are now defining apps as "guis that are flashy, sleek, use large rounded buttons, and have limited functionality', well, there's many of those out there. End rant. (the word app just sets me off)
'We are trying to prove ourselves wrong as quickly as possible, because only in that way can we find progress.' RPF
All I want is an option in the Control Panel that says "Completely disable Metro UI. I understand this will prevent me from installing, launching or utilizing Metro Apps. This will enable the classic Start Menu and will make the Classic Desktop your only operating environment." Problem solved. Just fucking humor us.
If there are no on screen visuals I'm lost.
This is very true. It's a problem with a lot of touch-centric UIs: There are no onscreen hints or anything to explain to you how to use the UI.
Anyone who has ever used a word processor can sit down with Microsoft Word and write a letter. There will probably be things you don't know how to do, so you'll end up searching the Ribbon to find them. But that's just it -- you can find them. There will be icons there and the icons will have labels that say things like "Insert Date/Time."
Metro, on the other hand, has a few clever icons, but they don't necessarily mean anything to someone who has never seen them before. Some of the other functions involve gestures or moving the cursor to just the right part of the screen to activate a feature. I found I had to stumble around awhile before I knew how some of the most basic navigational controls worked.
Note: I didn't say search around, as you'd have to do with the Ribbon. I said stumble around, meaning I had to try mouse movements and push icons without knowing what they were actually going to do. Inevitably that meant I'd end up activating controls I hadn't meant to. I might luck out and find the thing I want, or I might immediately think "Undo, Undo, Undo" ... but of course, Undo might have been the thing I was looking for in the first place. This is a lousy way to learn a UI. It's a step back from what we've grown accustomed to.
Breakfast served all day!
I'm really trying to work with this. Other than Metro, Windows 8 isn't bad. It's actually a marked improvement over Windows 7. The biggest change is the number of windows I can manage and keep open with 4 gigs of RAM. Memory seems to be cycling by itself with no third party software, registry hacks, or manual optimization. Silverlight is better on my 2gb Gforce card. Netflix is clean, and looking great. On Windows 7, the picture was muddier. So in terms of the things I care about (lots of open windows and netflix) Windows 8 is a boom.
What I'm not impressed with is the way Metro is locked down. I downloaded Visual Studio 11 beta so I could start writing Metro apps, and was immediately reminded that Microsoft will be approving any and all Metro apps, but they're letting me run my own stuff out of the kindness of their ever loving little hearts. That annoyed me, and it made me question my motivation for wanting to write Metro apps in the first place.
I mean, I can write an Android app today, compile it into an APK, and it'll run on any Android device within the scheme I compile for. Google doesn't and shouldn't care about the apps I write, and I like it that way. I don't really see the point of building something in the first place when someone who has nothing to do with anything can control my ability to publish it. If there's any chance of rejection at all, why should I bother to begin with?
I'm not learning new platforms because I like new platforms (well, I am, kina), I'm doing it because I want to have viable programs that I can do things with.
Screwing with my ability to publish my work is not a way to launch a new product.
I'm sorry. It's totally unacceptable.