4 Issues with windows phone:<p>1> It doesn't capture the "I WANT CONTROL" people or "I WANT SEXY ALUMINUM" people. These are significant, and vocal minorities on the two platforms. So all that is left is the not so particular middle.<p>2> It limits developers to Sandboxed C#. This means software written in C which is portable to pretty much every other device (Android included) isn't portable to here without a rewrite.<p>3> The simulators don't run in VM's on Macs. Why does this matter you ask? Because people putting out things for the other platforms OVERWHELMINGLY use Macs, due to the "Must have mac to make an iPhone app" requirement. So yes, you can dual boot to make this, but that costs an additional $150 for the OS as well. You might try to argue "why doesn't apple have to put out windows compatable SDKs", but you'd be ignoring the fact they're currently the dev environment which is the revenue leader, so aren't playing catchup, while MS <i>is</i> playing catchup.<p>4> It doesn't have any penetration to the crossplatform tools. It doesn't work in Adobe Flash Builder, it doesn't work in Titanium, it doesn't work in PhoneGap, it doesn't really work then for the people who publish on multiple platforms.<p>I think it's a beautiful project. I just think the guys running the developer relations programmers spend too much time buying iOS developer groups beer and not enough time making the toolchain usable by iOS and Android devs without hardware outlays and hard disk reformats.