At least in terms of native applications I've seen literally no differences; maybe Metro handles it better but Metro on the desktop is, well, Metro on the desktop.
PS - I know it is now called "Modern UI" but that name sucks.
A lot more detail about the mbp and 8: http://blogs.msdn.com/b/tonyschr/archive/2012/08/29/windows-...
eg here is one blog post from 2006, which in turn refers to guide written in 2001 http://blogs.msdn.com/b/greg_schechter/archive/2006/08/07/69...
iirc there was some similar blog-post series about high dpi stuff when windows 7 was released, but I couldn't find it now with google.
Once you get into a proportional mindset, the hardest problems tend to be related to text and images. One trick I learned for the latter was using vector art as much as possible and converting SVG images to XAML (care of XamlExport[1]). Then scaling no longer becomes an issue. For raster art, I would hope Metro has something similar to iOS's retina graphic substitution magic. Silverlight 4 didn't which was a bit of a drag.
Text was always a little trickier but when dealing with full screen apps I would usually just have some code that changed the text size based on the delta between the new and old window size.
That said, you mentioned that Metro will do image substitution a la iOS. Thats fantastic and something I sorely missed during my Silverlight dev days.
I can't answer the to specifics of how rendering is different between 7 and 8, but the frameworks released with 8 have or are moving towards vector and resolution-independent rendering.
http://www.zdnet.com/microsoft-design-language-the-newest-of...
I made that decision back in 2004 when my laptop had 1680x1050 resolution. Since then I've only gone higher and I've yet to have problems.
Windows seems to have handled this pretty well long, long ago so I have no idea what people are complaining about.
Look at this skype screenshot at 125% for example:
http://www.anandtech.com/show/5843/asus-zenbook-prime-ux21a-...
That screenshot you link to is of Skype, and I would not use Skype as a standard example for anything. Even if MS owns it now, it is a poorly designed program by today's standards.
The only UI problems I ever had with scaling was with iTunes, and that was at >150%. I write it off as Apple not optimizing the UI for Windows.
How does this in any way negate it's worth as an example of a problem? It's effectively saying "That problem, it's an invalid problem because I said so."
I didn't state the problem is invalid, I merely provided anecdotal evidence from my years of experience in using DPI scaling in Windows to demonstrate that it's a non-issue.
Which is the key factor here. It's not Windows' fault specifically, but it's a problem that occurs when using (very common software on) Windows. To the end user, what's the difference?
If the problem is with Windows, finding acceptable alternative software is unlikely, if it is possible at all. Even worse, users are likely to see the problem affecting most of the applications they use rather than just some specific applications.
I'd say end users would notice and care about the difference between those two scenarios.
If Skype and iTunes -- which together are probably installed (one or the other) on a huge percentage of home systems, and a nontrivial number of corporate ones -- are ugly at higher resolutions, then there's a serious problem.
Sure, they shouldn't write shitty software, but it's now Microsoft's problem due to how it impacts the platform as a whole. At least in the case of Skype, one assumes they could fix it (since they now own the product); iTunes is ... probably more complicated.
If people generally spend most of their time in IE/Chrome/Firefox,Word,Excel,PowerPoint... and they all look great and Skype and iTunes look bad, I'd expect people to complain about Skype and iTunes.
If, on the other hand, people spend a lot of their time in applications that look bad I'd expect them to have a broader complaint (which may or may not be about Windows since, by assumption, we are talking about people who don't understand what's going on under-the-covers).
You haven't met very many end users, have you?
The problem is that both the OS and popular apps need to support it, otherwise in most people's eyes it will seem like Windows is "broken".
Lots of screen real estate though.
With 175% zoom I get some weird(and reported) errors in Chrome: http://imgur.com/TCDMj
The HiDPI solution in ML is not really a solution for resolutions that are somewhere in-between normal DPI and HiDPI.
I enabled HiDPI mode, but then I got 1280x720 on 27"... And without it much of the texts on web pages are too small.
You make it sound like I'm blind or something. I'm just tired of reading far too small texts.
100 DPI is pretty much the industry standard, so if it feels awkward to you then it's not a problem with the iMac per se.
NeXTStep/OpenStep used bitmap icons.
Go to any etailer and check 1080p on laptop options: from 300 models you get 50 at best. There's very little choice too, AFAIK the Zenbook is the only 1080p ultrabook out there and I could only find 2 AMD laptops with HD screens.
Like I said before I don't know what's crazier: that a 10" tablet has a 2560x1600 screen for $399 or that a 15" laptop for $800 might not have a 1080p screen.
The irony is that its been years since I saw a sub-1080 monitor for sale, but XGA/720p laptops are still the norm.
Let's at least make 1080p the standard.
Would you care to mention some? My impression has always been that Gnome handles different DPI settings relatively well, but I'm no expert.
I've never had a problem using high DPI screens on Linux. There's a setting in xorg.conf, but I haven't had to touch it in years because the correct settings are usually auto-detected.
I don't use Gnome, though, so maybe it's causing problems?
Now all we need is linux to credibly support it as well, or at least a linux built for mouse use. There are still many, many usability issues in gnome with a high ppi screen.
Also, lets not forget how far mobile gpus have come in the last few years, it would have been impossible to push that many pixels with anything but the most minimal of 3d use cases.
It's a much more complex problem than linus would suggest by simply having oems switch panels. Witness how relatively complicated apple's solution is, which came after years of supposedly "somewhat" supporting hidpi. Use the hidpi macbook pro at 1920x on the ivy bridge gpu and it's still noticeably laggy at some 3d operations.