Love / H8
A Review of Windows 8 Consumer Preview

Microsoft’s next operating system, Windows 8, is now available in “Consumer Preview” form — a release designed to let potential customers know what to expect from it when it launches in around six months’ time. It’s probably a very good idea to give it six months to soak in, because just in case the tech media has entirely passed you by, it looks like this:

Metro Start Screen

Nary a Start Menu in sight. Microsoft has gone all-out with its minimal, colourful “Metro” design that appeared first on Windows Phone 7 before coming to the Xbox 360 and finally to the desktop/tablet OS itself.

I say “tablet” there because Windows 8 is very much focussed on the tablet — sometimes, it appears from the Consumer Preview at least, to the detriment of the desktop experience. It makes its point even before you first log in, with its photograph that overlays the login screen. How do you get from there to the login options? Swipe up. Or for a desktop user, the much more awkward click-and-drag-up. (Luckily, pressing a key also works.)

Where’s the Start button? There isn’t one. To get back to the Metro tiles, you swipe in from the bottom-left of the screen, or from the right and press the Start button that appears. Both are easy, if not exactly intuitive, gestures on a tablet but are very awkward with a mouse. The same applies for the task switcher (swipe from top-right). And Metro apps can’t be closed apart from by going to that task switcher and dragging an app off the panel. In practice, for the desktop user, this means relying on the Windows key, Alt-Tab and Alt-F4 instead of the mouse gestures that are just too annoying to use all the time.

The key usability ethos that drove Windows Phone’s Metro interface is that it should be “glanceable”; that users shouldn’t have to go into different apps or do complex things just to see the information that’s important to them. This idea has made it through to Windows 8 relatively intact — there’s a mail tile that shows your new mail, a calendar tile that shows upcoming appointments, and so on. It feels a lot like a phone or a tablet, but what it doesn’t feel much like is a real, multi-function, generic computer.

Windows 8 Calendar

Calendar

Windows 8 doesn’t break support for all the apps you’re used to, but it does add new Metro-style apps of its own on the top. They’re really, really pretty — and currently unfinished, though that’s par for the course for an unreleased operating system. Above, the calendar’s month view really shines in full screen (though you can’t show more than just your primary Google calendar). Below, the equally pretty and minimal mail app (that doesn’t support generic POP or IMAP accounts yet).

Windows 8 Mail

Mail

Some integration is very well done, such as the Pictures app which automatically shows pictures from Facebook, Flickr and SkyDrive:

Windows 8 Pictures - Flickr

Pictures

…but some is less well done, such as the “What’s New” page shown below. Huge amounts of wasted space make it largely unusable as a main way of interacting with the Twitter and Facebook feeds that it shows. (It’s also the interface’s only serif text, which is slightly jarring.) Hopefully this app will get a lot of attention before launch.

Windows 8 "What's New"

"What's New"

There are a few ugly lines and some odd incidences of 16px Arial bold too, such as in the weather app (below). On any other interface they’d go unnoticed, but given the smoothness and the emphasis on large, thin typefaces everywhere else in the GUI, they stand out.

Windows 8 Weather

Weather

By contrast the new Windows Store really nails the appearance, showing off how beautiful Metro can be. Again, as expected for a pre-release OS, the store is a ghost town with only a couple of dozen apps in total. Apps from the store install and update as expected, which may finally put an end to the manual effort of keeping Windows apps up-to-date, at the cost of putting more of the computing experience under Microsoft’s control. (Of course, you can still download and install apps without going through the store.)

Windows 8 Store

Store

The full list of installed applications isn’t on a Start Menu but is instead part of the system-wide Search functionality, just like on smartphone operating systems. Luckily you can get there just by typing on the Metro “Start” screen, so it works as a decent app launcher for keyboard-lovers.

Windows 8 Complete Menu

Search

As you can see, non-Metro apps are included in this list too, and when activated, the main problem with Windows 8 becomes apparent: schizophrenia.

It’s like there are two teams at work on Windows 8 (there probably are) and they refuse to talk to each other or share ideas. From a world of simple minimalism, geometric tiles and large thin fonts, the simple request for a file browser window drops you immediately into this:

Windows 8 Explorer

Explorer

Five menus worth of “ribbon” interface, icons in ribbons, icons in the title bar, minimise and maximise, location bars, side bars… The Explorer GUI would have looked at home in Windows 7, but against the rest of Windows 8 its needless complexity and over-engineering is staggering.

To the left of the screen are desktop shortcuts that bear no resemblance to your Metro “desktop shortcuts”. At the bottom of the screen, a taskbar that doesn’t include the Metro apps you have open. And of course no Start button, no hint to the novice user that there is a way back to the completely different interface they were using just now. (If you’re wondering, the corner-hotspot-gestures still work, bringing up weird semi-transparent overlays over the Windows desktop.)

For the many people who are going to hate the Metro interface, it’s nice that you can use Windows 8 largely from the traditional desktop — but if you don’t pin all the desktop apps you want to the taskbar, you’ll have to dip back into Metro to launch them. Unfortunately, for those people, there’s no compelling reason to upgrade. The desktop experience is nearly identical to Windows 7, and all Windows 8 adds is a weird extra GUI layer that you hate.

For the people, myself included, that love the Metro interface, we have the opposite problem. Simple productivity tasks can be done from Metro, but to get any real work done — a web browser that supports more than 10 tabs, say, or a word processor, or a game — you’ll be switching back to the desktop interface far more often than you’d like.

Windows 8 Settings

Settings

With Windows 8, Microsoft have set themselves a monumental challenge. Rather than follow in Google and Apple’s footsteps by adapting their mobile OS for tablets, they have chosen to differentiate themselves by adapting their desktop OS instead — the same desktop OS that is used by an estimated 90% of all computer users. If they fail, it will have been an expensive experiment that could cost them ground in the desktop market as well as the tablet market. If they succeed, they will have stolen Apple’s crown as the greatest innovator in desktop operating systems.

This time next year, we’ll know for sure.

In the mean time, I’m rebooting into Linux.

The UI of Least Resistance

I was working up to a blog post on Ubuntu‘s new “Unity” interface a couple of days ago, but repeatedly stalled when it came to making a point. The only point I could come up with was essentially just “I don’t like this”, which isn’t the greatest of subjects for a blog post — to say nothing of the hundreds who have trodden that territory before me.

Ubuntu's Unity interface

Ubuntu's Unity interface (image credit: webupd8.org)

It’s a fairly bold new direction for Ubuntu’s UI, and the first time their default interface has really diverged from what the upstream GNOME project provides. Now I don’t like it for a number of reasons: it’s slow, it doesn’t provide some basic functionality, other functionality is really well hidden (Go on, re-order your icons. Try it.) and it’s got an “our way or nothing” approach to handling workspaces.

On one hand, as a software guy whose main specialisation is user interface design, I understand the urge to try new UI paradigms as often as possible, on the grounds that sooner or later you’ll discover something that really is better than what you currently have. On the other hand, I quietly despair at how far off that “something better” seems.

Take, for example, me. I’m a UX person, and a perfectionist when it comes to interfaces. I’m irritated by slightly-wrong fonts and icons a couple of pixels out of alignment. I love new things, new ways of organising and displaying data. I’m big on augmented reality. And my desktop looks like this:

Bare XFCE Desktop

Now I think that’s aesthetically pleasing, but in terms of functionality, it resembles nothing quite so much as:

Windows 95 Desktop

Yeah, that.

The only notable exception is GNOME-Do (think Launchy on Windows or Quicksilver on OS X), which I use exclusively for launching apps. The main menu, lower left, only gets used if I forget the name of something. Aside from that, I’m using my computer in exactly the same way I was 16 years ago.

The reason for that, as far as I can tell, is that it is the UI of least resistance. In sixteen years, probably 99% of my computer-using time has involved an interface that’s very similar to that one. Sure, there are certainly better UIs out there. Maybe from an objective point of view, Unity is one of them. But for more than half of my life, my brain has been slowly optimising itself for the Windows 95 style interface.

To become the “next big thing” in desktop UI, a new paradigm must not only be better than what came before, it must be so much better that our brains don’t mind losing half a lifetime’s worth of learning.

That’s a milestone I haven’t seen reached lately on the desktop, and a fear we may not see it reached before “the desktop” stops being a thing.

An Ode to Sharepoint

At a loss for other, more pleasant subjects to blog about, I will instead write about my nemesis, that being that has brought naught but pain to my life. I speak, of course, of Microsoft Sharepoint.

To upgrade one’s version of Windows — Vista to 7, say — is by and large a pretty painless experience for the home user. Office, likewise — there’s no dread that your Office 2003 files will be completely unopenable in Office 2007. So why is the poor sysadmin not afforded the same easy upgrade path?

In order to move an existing SharePoint Services 2 website to a new network with Microsoft Office Sharepoint Services 2007, one must:

  1. Learn more than is healthy about the workings of Sharepoint and IIS (2 days, d10 SAN)
  2. Back up the original site to disk (using stsadm.exe not smigrate.exe, as the latter is broken) (5 hours, 13 GB)
  3. Install Windows Server, IIS, SQL Server and Sharepoint Services 2 on a new machine (1 hour)
  4. Configure said IIS, SQL and Sharepoint (1 hour)
  5. Restore the Sharepoint site from disk onto the new machine (>8 hours, >120 GB, d10 SAN, fails unrecoverably when out of disk space)
  6. Perform an in-place upgrade to Sharepoint Services 3 (Several hours, 40 GB, may fail unrecoverably)
  7. Back up this site to disk (5 hours, 15 GB)
  8. Configure MOSS 2007 on the destination server (2 hours, 24 Google searches, d10 SAN)
  9. Restore the disk backup to the MOSS 2007 server (5 hours, 40 GB, may fail right at the end if previous step performed incorrectly, d100 SAN if this occurs).
  10. Manually recreate permissions on every Sharepoint site since all the users are now part of a new domain (8 hours, d10 SAN)
  11. Perform a ritual to offer Great Cthulhu the souls of Microsoft’s Sharepoint development team (d30 SAN, remarkably quick by comparison)

I began this task on Tuesday afternoon as a mildly knowledgeable Sharepoint user with virtually no admin experience. By Thursday afternoon, I may have been our company’s most experienced Sharepoint-wrangler. On Friday morning, I started the above procedure. We are now on Step 5. 200 people are expecting to have Sharepoint access tomorrow. They have not a snowball’s chance in R’yleh.

All Bugs Are Shallow… Except This One

In his essay “The Cathedral and the Bazaar”, Eric S. Raymond coins the phrase “given enough eyeballs, all bugs are shallow” — meaning that with enough testers and enough programmers, it is possible to diagnose and fix any software bug.

So why can’t my computer suspend and resume properly?

The concept of ‘suspend’ — or ‘sleep’, or ‘standby’ — mode, whereby the computer dumps its internal state to RAM then enters a low-power state with its processor and other hardware turned off, is not new. The ACPI standard has been kicking around for 14 years now, a very long time compared to the life cycle of an operating system. These days, with laptop use on the rise, it’s a very common thing for users to want to do. And yet resuming from suspend is still hit-and-miss.

Why do I find it more reliable in Ubuntu than openSUSE for the same base kernel? Why does GNOME fare better than KDE? Why does my WiFi sometimes not come back? Why, with Microsoft’s million- if not billion-dollar operating system budgets, with Intel and AMD and nVidia’s decades’ of driver experience, is suspend and resume still frequently an issue even on Windows?

Only Apple, with its closed hardware / software ecosystem, seems to have cracked it.

I’d hate to think of that as the only way to a bug-free existence — I’m very fond of the idea of an open ecosystem where I can run whatever software I want on whatever hardware I want. But I’m worried. Is the range of (IBM-compatible, ACPI-supporting) hardware out there just too diverse and too widely different in its support for suspend-and-resume? Is it just infeasible for software to perfectly implement it on all devices?

Has hardware created the one software bug that, for any reasonable number of eyeballs, isn’t shallow?