4 ms·

As most new apps start to be built on UWP that issue will go away. Also, I am not sure what DPI issues you're facing but I have run W10 on my rMBP for quite so

As most new apps start to be built on UWP that issue will go away. Also, I am not sure what DPI issues you're facing but I have run W10 on my rMBP for quite some time and it's been thoroughly pleasant. Perhaps your issues are fuzzy text due to mixed DPI, multi monitor setup?

LeoNatan25 10y ago
I am not using UWP apps. Most of the software I use on Windows are either MFC or Windows Forms. These can also be DPI aware and render correctly, but they require proactive developer support, which is not something that is happening in the Windows developer world right now. Either software is abandonware (but still works), or issues are open and remain open or are simply closed with "won't fix" status. Most developers see this as a non-issue or very low priority. I mean, even Chrome does not support high DPI from what I remember. It looked terrible. Linux world is in the same boat. It's even worse there, because a lot of the toolkits don't support high DPI modes or are buggy, and developers there are even less interested or have the know-how to fix issues. With the emergence of cheaper 4K monitors, perhaps we'll see a change to the better, who knows. Multi-monitor support is another issue entirely.
- Pxtl 10y ago
  What's funny is that supporting high DPI on a winforms app isn't even hard. Even if you size all your widgets in pixels, if you just do a little playing with the scaling options and just try out the ui on high DPI, it seems to work pretty well except for the old icons. I forgot what the setting is called, but theres a (non-defaukt) scaling option or two that seemed to "just work" as it were. The harder part is to consistently fix everything that uses the old win2000 8pt default font instead of a modern one.
LeoNatan25 10y ago
Also, it's not just scaling. Often even if an application scales somewhat correctly, often some elements don't, because it's using some open source that draws something in a terrible manner. Or, assets look blurry because of "16x16 is all you really need" mentality. This used to happen on OS X in the first months, but very quickly and uniformly, developers just fixed their custom code and assets. Not so with Windows developers, sadly.
dingo_bat 10y ago
UWP is dead imo. Microsoft is ignoring the signs that can tell it to accept it gracefully. There is not one uwp app that I use. They are just not reliable. A splash screen will show up, and then disappear. The app won't launch. You open the fb messenger app and then switch desktops to work. 2 hours later the messenger is nowhere to be found. It just disappears. No error no notification. Nothing. First I thought it's fb incompetence. But this happens with the built in photos app. The built in mail app. Even shell elements (start menu, notification shade) are buggy. Windows 10 is a great os as long as you avoid any interaction with uwp stuff.
kartickv 10y ago
UWP apps have a lot of limitations compared to WPF/Win32 apps. As I understand it, UWP apps can't record audio in the background or act as a Bluetooth accessory, to give two examples. So, even if a developer is willing to invest the time to rewrite an app to use UWP, the app will lose a lot of functionality. Microsoft has again poorly architected their APIs. Unlike macOS, where there's no penalty to adopting the latest APIs. It's not as if, to use the Touch Bar, you have to give up access to other capabilities, like recording audio in the background. More information: https://kartick-log.blogspot.in/2016/08/how-powerful-is-uwp-compared-to-ios-or.html https://kartick-log.blogspot.in/2016/08/how-powerful-is-uwp-...
- snuxoll 10y ago
  I mean, you can just use WPF + the desktop bridge in these cases. There's still some work for the desktop bridge to catch up, but it's perfectly feasible (aside from, you know, feeling like a traditional Windows desktop app vs a "Modern" one without a lot of work styling WPF controls).

LeoNatan25 10y ago

I am not using UWP apps. Most of the software I use on Windows are either MFC or Windows Forms. These can also be DPI aware and render correctly, but they require proactive developer support, which is not something that is happening in the Windows developer world right now. Either software is abandonware (but still works), or issues are open and remain open or are simply closed with "won't fix" status. Most developers see this as a non-issue or very low priority. I mean, even Chrome does not support high DPI from what I remember. It looked terrible. Linux world is in the same boat. It's even worse there, because a lot of the toolkits don't support high DPI modes or are buggy, and developers there are even less interested or have the know-how to fix issues. With the emergence of cheaper 4K monitors, perhaps we'll see a change to the better, who knows. Multi-monitor support is another issue entirely.

Pxtl 10y ago
What's funny is that supporting high DPI on a winforms app isn't even hard. Even if you size all your widgets in pixels, if you just do a little playing with the scaling options and just try out the ui on high DPI, it seems to work pretty well except for the old icons. I forgot what the setting is called, but theres a (non-defaukt) scaling option or two that seemed to "just work" as it were. The harder part is to consistently fix everything that uses the old win2000 8pt default font instead of a modern one.

LeoNatan25 10y ago

Also, it's not just scaling. Often even if an application scales somewhat correctly, often some elements don't, because it's using some open source that draws something in a terrible manner. Or, assets look blurry because of "16x16 is all you really need" mentality. This used to happen on OS X in the first months, but very quickly and uniformly, developers just fixed their custom code and assets. Not so with Windows developers, sadly.

dingo_bat 10y ago

UWP is dead imo. Microsoft is ignoring the signs that can tell it to accept it gracefully. There is not one uwp app that I use. They are just not reliable. A splash screen will show up, and then disappear. The app won't launch. You open the fb messenger app and then switch desktops to work. 2 hours later the messenger is nowhere to be found. It just disappears. No error no notification. Nothing. First I thought it's fb incompetence. But this happens with the built in photos app. The built in mail app. Even shell elements (start menu, notification shade) are buggy. Windows 10 is a great os as long as you avoid any interaction with uwp stuff.

kartickv 10y ago

UWP apps have a lot of limitations compared to WPF/Win32 apps. As I understand it, UWP apps can't record audio in the background or act as a Bluetooth accessory, to give two examples. So, even if a developer is willing to invest the time to rewrite an app to use UWP, the app will lose a lot of functionality. Microsoft has again poorly architected their APIs. Unlike macOS, where there's no penalty to adopting the latest APIs. It's not as if, to use the Touch Bar, you have to give up access to other capabilities, like recording audio in the background. More information: https://kartick-log.blogspot.in/2016/08/how-powerful-is-uwp-compared-to-ios-or.html https://kartick-log.blogspot.in/2016/08/how-powerful-is-uwp-...

snuxoll 10y ago
I mean, you can just use WPF + the desktop bridge in these cases. There's still some work for the desktop bridge to catch up, but it's perfectly feasible (aside from, you know, feeling like a traditional Windows desktop app vs a "Modern" one without a lot of work styling WPF controls).