The Windows Interface You Didn’t Like, For Linux

If you were asked to pick the most annoying of the various Microsoft Windows interfaces that have appeared over the years, there’s a reasonable chance that Windows 8’s Metro start screen and interface design language would make it your choice. In 2012 the software company abandoned their tried-and-tested desktop whose roots extended back to Windows 95 in favor of the colorful blocks it had created for its line of music players and mobile phones.

Consumers weren’t impressed and it was quickly shelved in subsequent versions, but should you wish to revisit Metro you can now get the experience on Linux. [er-bharat] has created Win8DE, a shell for Wayland window managers that brings the Metro interface — or something very like it — to the open source operating system.

We have to admire his chutzpah in bringing the most Microsoft of things to Linux, and for doing so with such a universally despised interface. But once the jibes about Windows 8 have stopped, we can oddly see a point here. The trouble with Metro was that it wasn’t a bad interface for a computer at all, in fact it was a truly great one. Unfortunately the computers it was and is great for are handheld and touchscreen devices where its large and easy to click blocks are an asset. Microsoft’s mistake was to assume that also made it great for a desktop machine, where it was anything but.

We can see that this desktop environment for Linux could really come into its own where the original did, such as for tablets or other touch interfaces. Sadly we expect the Windows 8 connection to kill it before it has a chance to catch on. Perhaps someone will install it on a machine with the Linux version of .net installed, and make a better Windows 8 than Windows 8 itself.

20 thoughts on “The Windows Interface You Didn’t Like, For Linux

  1. “Unfortunately the computers it was and is great for are handheld and touchscreen devices where its large and easy to click blocks are an asset. Microsoft’s mistake was to assume that also made it great for a desktop machine, where it was anything but.”

    Least it wasn’t a Minority Report style interface. Directing the wrong kind of traffic.

    1. Microsoft Bob was a masterpiece! fond of some of the other shells like it, too. if I had the time and will, I’d make all my web interfaces like it; I tried it on a public web server for navigating to games and utilities but it was just too much of a trouble to maintain and wound up being the fastest I’ve ever abandoned a rewrite (I think it was live for only maybe 2 months).

    1. That’s because Win95 was designed by a definite paradigm. Everything had a point and a purpose.

      Then everyone started to “think outside the box” and make cool shit instead.

      Like most Linux distros that tried to borrow elements from macs and windows machines haphazardly without really thinking what it’s supposed to mean. Is a window a program or a document? Should we have two taskbars or one, or something else? Nevermind, we’ll just add virtual desktops and make them into a spinning cube!

    2. One notable difference in how it was made: usability testing and iteration. Microsoft hired actual designers rather than engineers to build the user interface, and they quickly iterated different designs with actual users, so it wasn’t just software developers going “This is how I would use it.” or “Here’s how Apple does it”.

      https://socket3.wordpress.com/2018/02/03/designing-windows-95s-user-interface/

      It’s an interesting read of the troubles and problems they had to solve:

      All but the most advanced users did not understand how to manage overlapping windows efficiently. Beginners had the most trouble-when they minimized a window, they considered it “gone” if it was obscured by another window. We heard many stories from educators (and witnessed in the lab) how users caused the computer to run out of RAM by starting multiple copies of a program instead of switching back to the first copy.

        1. It was when 2/3rds of the population had never used a computer. People had no idea how anything is supposed to work.

          Example: user wants to paste a file into the same folder, so they can then drag the duplicated file somewhere else with the mouse. Operating system doesn’t allow that action.

          The action makes sense if you think of the files as physical objects: first it needs to exist before something can be done with it. First you make a copy, then you move the copy. The copy of the file existing invisibly “in potential” is not intuitive. You could try to fight the user over this point and demand them to browse to the destination folder before selecting “paste”, but that’s not helpful. Throwing an error message is the last thing you want to do, because that would be hostile to the user. That will just put the user off by denying their intuitions, and stop them from completing the action.

          Solution: let the user do what they’re trying to do – just change the file name slightly so both copies can exist in the same folder.

          Eventually they’ll learn better ways to it.

      1. What is different now?

        https://microsoft.design/articles/a-glimpse-into-the-history-of-windows-design/

        Working with developers and PMs is so different now because everybody gets the value we bring. In the past, design had to prove its value to our business and show how good design positively affects user experience, and thus the bottom line. Our leadership has matured over the years, and we had some amazing design leaders in the past who were champions for design and gave us a voice in Microsoft. Today, you cannot build a product without having good design.

        Translation: “Our bosses don’t bother to read our test reports anymore and just let us do whatever.”

      2. Nearly everyone e in 2026 still freak out when they click on a link in a chat during a Zoom meeting, and think that they ‘lost” the zoom software. Running multiple programs at the same time, even though you can’t see them, is a concept nearly nobody graps.

      1. It replaced Motif standard

        Yep, and as the Win95 usability study pointed out:

        Beginning users and many intermediates relied almost exclusively on visible cues for finding commands. They relied on (and found intuitive) menu bars and tool bars, but did not use pop-up (or “context”) menus, even after training.

        What’s the main menu feature in Motif? A pop-up menu you get when you click the desktop. The complete opposite of what users found intuitive and useful. That’s why the Start button.

  2. the win2k start menu was about all i ever needed. i really didn’t like that they upgraded it in windows 7, of course that menu kind of grew on me, metro i wasn’t even doing that and i didn’t upgrade to 8/8.1 without classic/open shell.

Leave a Reply

Please be kind and respectful to help make the comments section excellent. (Comment Policy)

This site uses Akismet to reduce spam. Learn how your comment data is processed.