Windows 8 designers are blind.


Recommended Posts

I don't see what the problem is here. You can find some these so called "inconsistencies" in windows 7 too.

<images snipped>

The problem is that the inconsistencies have been plaguing Windows since the 3.x days and should have been eliminated by now. How hard can it be to hire decent graphics designers and themers?

  • Like 2

One of the problems with Microsoft is the lack of UI consistency across product teams. Take a look at the following screenshot:

capture.png

Four MS programs, four ever so slightly different UIs. How hard can it be to design a consistent HIG for Windows and all first-party applications, and force the various units within Microsoft to adhere to it?

Few things here, while I agree the apps need to look the same, I have to point out that VS 2012 and Office share enough similarities that trying to compare the two is inconsequential. Explorer, however, should have been altered to match. Kinda disappointed in that. Notepad, though, is an app so ancient, it's just excess baggage at this point. It should be stripped out in favor of Wordpad, which HAS been updated with the Ribbon UI. It wouldn't take much work to match it up with the rest.

The problem is that the inconsistencies have been plaguing Windows since the 3.x days and should have been eliminated by now. How hard can it be to hire decent graphics designers and themers?

I don't know. Didn't even notice them until I saw this thread, and frankly, I'm not bothered at all. I'm sure that applies to a huge majority of users too.

While I agree these are mistakes in the UI and should have been fixed. I believe though most people barely register, if at all, that there are some of the mistakes the OP referred to.

I suppose in the case of Wordpad not matching Word, for example, is due to being released at different times or it could be due to one being a freebie and the other being a paid program.

They are close enough that most people won't care.

I do find in Windows 8 that the theme for the desktop is not "Metro" enough. If they wanted to make it "Metro", they could have done a lot more.

Few things here, while I agree the apps need to look the same, I have to point out that VS 2012 and Office share enough similarities that trying to compare the two is inconsequential. Explorer, however, should have been altered to match. Kinda disappointed in that. Notepad, though, is an app so ancient, it's just excess baggage at this point. It should be stripped out in favor of Wordpad, which HAS been updated with the Ribbon UI. It wouldn't take much work to match it up with the rest.

Office and VS 2012 are different enough to notice. Again: Microsoft need to use one consistent HIG and one well-designed UI tool kit for all their applications. It's ridiculous how with every new version of Windows/Office/Visual Studio there are inconsistencies.

Office and VS 2012 are different enough to notice.

Not really. The only difference is that one uses the Ribbon and one doesn't. I'm not sure why VS doesn't have the Ribbon yet, but they are utilizing the same UI guidelines and icon design. Office is also incomplete and expected to change before the finalized version comes out.

Not really. The only difference is that one uses the Ribbon and one doesn't. I'm not sure why VS doesn't have the Ribbon yet, but they are utilizing the same UI guidelines and icon design. Office is also incomplete and expected to change before the finalized version comes out.

Look closely. Office uses a white window chrome whereas VS2012 uses a light grey one. The window buttons are ever so slightly different. The window title in VS is left aligned, whereas in Office it is centred. The differences may be small to you, to me they stand out.

I know Office 2013 isn't final yet - but given Microsoft's history of UI design I don't have many hopes for real improvements.

  • Like 2

Look closely. Office uses a white window chrome whereas VS2012 uses a light grey one. The window buttons are ever so slightly different. The window title in VS is left aligned, whereas in Office it is centred. The differences may be small to you, to me they stand out.

I know Office 2013 isn't final yet - but given Microsoft's history of UI design I don't have many hopes for real improvements.

Yes there are differences, but nothing IMO to get hung up about, especially considering what they have done, and needed to do these past few years. They transformed Windows into a new OS, ported the code for both Windows and Office to ARM chips, and were busy insuring compatibility with older apps. Microsoft is a lot more consistent than they have been past years (Windows 7 is a mess of new, old, and ancient), but things take precedence over others when designing and coding.

Yes there are differences, but nothing IMO to get hung up about, especially considering what they have done, and needed to do these past few years. They transformed Windows into a new OS, ported the code for both Windows and Office to ARM chips, and were busy insuring compatibility with older apps. Microsoft is a lot more consistent than they have been past years (Windows 7 is a mess of new, old, and ancient), but things take precedence over others when designing and coding.

you might be right, but wouldn't it be nice if the desktop side of Win8, and all the desktop in house apps, including VS2012, SQL Server,... would have the same style.

I wouldn't mind if everything looked like the Office 2013 style.

That would make MS look so much more professional in my opinion

  • Like 2

you might be right, but wouldn't it be nice if the desktop side of Win8, and all the desktop in house apps, including VS2012, SQL Server,... would have the same style.

I wouldn't mind if everything looked like the Office 2013 style.

That would make MS look so much more professional in my opinion

Don't get me wrong, I agree, and I think they're getting closer to doing that, it's just I think they've had their plates full these last few years with other things needing done first.

Notepad, though, is an app so ancient, it's just excess baggage at this point. It should be stripped out in favor of Wordpad, which HAS been updated with the Ribbon UI. It wouldn't take much work to match it up with the rest.

No. Notepad should and must remain the lightest and fastest text editor out there on Windows.

  • Like 3

We can describe the visual part of Windows 8 with one word. Clusterfu*k. This new RTM theme is disgusting and amateurish. Every single Windows 8 concept posted here on the forums is better than this crap. Desktop isn't going anywhere for the next 10-15 years at least, so I'm really hoping they'll make it pretty in Win9. MS should fire all designers and hire young people with great ideas.

Notepad is still used by a lot of coders, there's no need to remove it from Windows. I'm sure if you're concerned about the 189 KB of disk space the executable consumes you could always come and join us in the 21st century.

No. Notepad should and must remain the lightest and fastest text editor out there on Windows.

Speaking as someone who deals with large text files on a daily basis, Lightest maybe, but fastest I could not disagree with you more. I definitely disagree with Dot Matrix saying it needs to be removed (Wordpad is not a good text editor), but there are definitely improvements to be made in the basic notepad when opening large text files, or dealing with non-native line endings. Basic things that every other text editor has had sorted for years.

It's also a good candidate for metro-ization too. Not necessarily needing a ribbon and the like, but it could certainly be simplified and modified to fit in with the rest of Windows 8 very trivially.

  • Like 3

Couldn't they simply build a plain text mode into WordPad and merge the two?

Just no. Notepad just does its job more than right. It's supposed to produce text files which at most, can change their font.

No need for fancy UI to do that.

http://www.nytimes.c...k-002.html?_r=1

http://pc.net/helpce...epad_vs_wordpad

Edit:

@Majesticmerc

Just read your post, and yes, it actually could receive some changes :p.

But why it isn't the fastest?

The millions of pages of blog posts on B8 about 'reimagining' Windows and the new 'Desktop experience' may claim different, but it is quite obvious 99% of the effort was on Metro/WinRT and the desktop was hacked together using whatever spare resources they could find, it is clearly a very distant afterthought.

I wish some of the designers of products like Zune/Metro were allowed to work on the desktop as well. In many ways desktop is worse than in Windows 7.

  • Like 2
:

@Majesticmerc

Just read your post, and yes, it actually could receive some changes :p.

But why it isn't the fastest?

For small files it's fine, but as the files get larger it just keels over and dies. Conversely I've seen notepad++ open files several gigabytes in size without so much as pausing.

The millions of pages of blog posts on B8 about 'reimagining' Windows and the new 'Desktop experience' may claim different, but it is quite obvious 99% of the effort was on Metro/WinRT and the desktop was hacked together using whatever spare resources they could find, it is clearly a very distant afterthought.

This is what I think too. Don't get me wrong, I like the new desktop theme, but it could have used more polish.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • The funny thing here is that like 70% or so of the web browser users use 'Google Chrome' as web browser. What I don't understand is that why on earth would ANYONE choose 'Google Chrome' on Windows when 'Microsoft Edge' is not just better in most things, but it's already there right out of the box for the Windows users. Microsoft Edge has less data collection (yes, that's a fact), less RAM usage and is more optimized for Windows (as it's a Microsoft product) right out of the box. Sure, the way Microsoft is pushing Microsoft Edge on users might not be the best way of doing it and might need to change. But I would never choose 'Google Chrome' over 'Microsoft Edge' today anyways. I'm sure there was a period back in the days when 'Google Chrome' actually was better in most things, but that period is not today.
    • JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more by David Uzondu Image via JetBrains IntelliJ 2026.1.3 from JetBrains has landed, bringing several highly requested bug fixes that target common UI glitches and terminal rendering issues. If you run tmux inside the integrated terminal, the IDE no longer renders the cursor above the active line. The Markdown preview bug, which was fixed in this release, had annoyed developers for quite some time, as the preview pane failed to render images saved outside the project directory. Instead of displaying the actual image, the IDE simply showed a broken image icon, a problem that stuck around for two years before this update. Over on Windows, developers running WSL can now use wsl.exe to spin up their environments without losing terminal functionality. In previous builds, launching a terminal shell with something like wsl.exe -d ubuntu inside a Windows-based project broke both shell integration and active process detection. Other bug fixes in this release include: An issue where Gradle sync incorrectly reported success as a failure on WSL when using Gradle 9.5.0. A syntax highlighting bug that flagged valid Java for-loop initialization blocks with multiple statements as incorrect. A warning bug that triggered a false non-null local variable alert when using JSpecify annotations. A database generation bug that hid the option to use a DELETE statement instead of a TRUNCATE checkbox. A Kotlin highlighting failure where an assertion error in the Gradle redundant library inspection broke error highlighting. A UI bug where the ComboBox popup lacked a maximum height restriction. A Snowflake syntax error where DataGrip failed to support the "create temp" command. A Svelte syntax parsing failure that incorrectly flagged quotes inside inline expressions. A VCS repository manager deadlock that triggered thread pool exhaustion. A memory leak where the LazyTree component kept all previous versions of a tree in memory. IntelliJ 2026.1.3 is the third bug fix release for the IntelliJ 2026.1 series. The first one landed back in April with a fix for the WSL Python interpreter freeze, another fix for guest participants using Emmet abbreviations, and corrected WildFly server deployment errors.
    • That stupid annoying Sign in with Google on all these sites now... get the fk outta here
    • I was just being silly based on David Uzondu's comment ☺️
    • The unified inbox, when it arrives, will be a powerful argument for those who have > 1.
  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      469
    2. 2
      PsYcHoKiLLa
      243
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      73
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!