As C++ is the native language for the UWP, surely it would map more neatly to the platform?
And the well-known performance and memory advantages, however small, are critical for mobile devices. I don't think Microsoft should commit long-term to C# on mobile just as both Apple and supposedly Google are migrating to Swift as the future of their platforms, for good reason.
> And the well-known performance and memory advantages, however small, are critical for mobile devices.
Windows Phone is many things, and few of those things are good. But in terms of UI responsiveness and overall speed, it puts my android to shame and competes with my iPhone.
And the security story of unmanaged languages is perilously bad. I don't see how people justify it anymore.
Actually, I would buy right away. Apple generally sources higher-binned (higher quality) components early on. i.e., only Samsung panels when the Retina MBP first launched in 2012.
Broadwell will be perfectly capable of driving the display.
The Air is 0.68" at the back. The Pro is 0.71". There's not much room there for a distinction between "thicker Air" and "thinner Pro," even if we think they'd be willing to make the Air less wedgey.
And when Broadwell chips roll out they will be placed in the Pro just as easily as the Air. They're both on Haswell right now.
Product differentiation matters to Apple. I just don't think a slightly slower processor and a 0.01" thickness cuts it.
The video segment in question starts at 8:40, though the entire video and its predecessor are well worth a watch.
Monty also tried making the argument against 24/192 music in written form in the past: https://web.archive.org/web/20130115154647/https://people.xi...