News for hackers. Stuff that matters.
Re:Retina MacBook Pro Review: The Age of the High-Resolution PC by rsynnott on Monday June 18, 2012 @07:44AM (#4125939)
> Back when WPF was still called Avalon, Microsoft were pushing the technology as a solution for the soon-to-be-arriving high-dpi displays

Although they were quieter about it, it has been quite clear that Apple was interested in resolution independence since at least 10.4, when such features started to show up.

Remember that very few third-party Windows applications use WPF. Most first-party stuff, even, doesn't use WPF. We're seeing on the retina Macbook that, while most Cocoa apps work well enough, most non-Cocoa apps are at least somewhat broken; imagine how much worse this effect would be on Windows, where so few apps use the current UI toolkits.

Re:Retina MacBook Pro Review: The Age of the High-Resolution PC by stusmith1977 on Monday June 18, 2012 @08:23AM (#4126073)
It's a chicken-and-egg situation, agreed, It just seems really strange to me that they spent so much effort pushing and developing the software side, without putting any effort into the hardware, when the two clearly have to go hand-in-hand.

Microsoft had the software stack ready - imagine if they had released (via partners) high-dpi laptops and screens shortly afterwards? That actually might have made a Windows machine a compelling and desirable product, instead of just an expensive way to run a browser.

Re:Retina MacBook Pro Review: The Age of the High-Resolution PC by rsynnott on Wednesday June 20, 2012 @10:44AM (#4137203)
Apple had a rather similar software stack ready, though; both worked on the basis of a point being a fractional number of pixels. The trouble with this is that while it tended to more or less work for simple things, for complex things, particularly where the programmer was drawing stuff, it was (a) somewhat inefficient and (b) very hard to get right. Apple used to periodically have talks at WWDC about how to get ready for independence back in 2006 or so, but it was clear that few developers were doing so successfully.

This new approach, where you have a point be an integer number of pixels, possibly with scaling after the fact (as with the non-standard resolutions available on the retina MacBook) is far simpler for developers, so more likely to work out okay.