3 ms·
No, they are exactly the same. Just a separate build. My point was that by writing software for Metro you are writing it for every future PC purchase, and altho
by MatthewPhillips 14y ago
No, they are exactly the same. Just a separate build. My point was that by writing software for Metro you are writing it for every future PC purchase, and although a lot of those won't be using Metro much, the sheer number of people who can use Metro is going to eclipse even the iPad. So the potential is obviously great.
- WiseWeasel 14y agoI understand the logic, and there's something to be said for being a big fish in a small pond, and the exposure of being one of the first to support the platform. But in the face of exploding iPad and Nexus 7 sales, I must admit I'd be pretty nervous investing heavily in touch-focused software for Windows, in the hopes that a market pans out. If supporting Metro without leaving mouse and keyboard users behind is possible, then it might seem more viable to me. The choice between dropping support for Windows 7- and maintaining two code bases raises the stakes for many developers. My understanding is that the only way to support Windows 7- and 8 in a single app is to make it non-Metro. So most developers must then choose between supporting Windows 7 and Windows RT, with the latter unproven.