Linked by Thom Holwerda on Thu 27th Aug 2015 23:18 UTC
Windows This hit the news yesterday.

Microsoft released Windows 10 four weeks ago today, and now the company is providing a fresh update on its upgrade figures. 14 million machines had been upgraded to Windows 10 within 24 hours of the operating system release last month, and that figure has now risen to more than 75 million in just four weeks.

As somebody who uses Windows every day, and who upgraded to Windows 10 a few weeks before it was released, let me make a statement about all the positive Windows 10 reviews that not everyone is going to like. There are only two reasons Windows 10 is getting positive reviews. First, because it's free. This one's a given. Second, and more importantly: Windows 10 is getting positive reviews because none of the reviewers have forced themselves to use nothing but Metro applications.

Here's the cold and harsh truth as I see it: despite all the promises, Metro applications are still complete and utter garbage. Let me explain why.

Permalink for comment 616796
To read all comments associated with this story, please click here.
RE: Win32 vs Metro
by dpJudas on Fri 28th Aug 2015 03:12 UTC in reply to "Win32 vs Metro"
dpJudas
Member since:
2009-12-10

I haven't installed Windows 10, so can't comment on the quality of metro/universal apps (or the lack thereof), vs how they are on Windows 8. But if your main complaint is the lack of consistency, how is that any different than Win32 apps? Those haven't been consistent for at least a decade; seems that every software dev thinks they have to gussy up the UI so that the app looks completely different from every other app on the computer.

Personally, I like consistency in my apps, so find this EXTREMELY aggravating. If I want to do any skinning, I'll do it at the OS level.

This is a bit complicated subject, but part of the problem is that theming gets really hard once applications get their own image and font assets. In classical Win32 (and Linux UIs) you had a theming engine like uxtheme.dll that would render the widgets in their proper theme. This gave the consistency that Thom and you are asking for.

But since then we had the world of websites each with their own style and looks. An application restricting itself to just using the controls offered by uxtheme will find itself to look really dated (it will look like a MFC application). Basically the system used by uxtheme isn't flexible enough to create visually rich applications ala what you see on a website.

So what you're seeing going on in Windows 10 is that half the context menus use uxtheme (mostly explorer and such). The other half uses their own custom design. And Microsoft isn't being consistent about it even when the custom designed menus are supposed to follow a general OS theme.

I'm not that well versed in WPF/XAML, but my guess is that either there is no theming engine at all, or its way too primitive to support the applications. You can see similar inconsistencies in newer Visual Studios too where there's an occasional label here and there with a wrong font size.

Reply Parent Score: 3