Not an iOS developer, but, say they did extend this, what's to stop a developer taking the (presumably MIT licensed code), using it within his app to get that on iOS too? I guess this doesn't work if it's being backed by some Windows feature, but otherwise?
That doesn't make much sense because iOS already comes with implementations for all these frameworks. You're kinda asking "what's to stop a developer from including wine into his windows app so it can run on windows?"
Yes totally pointless so long as they were strictly replicating iOS, but people seem to fear Microsoft extending the APIs.
iOS developers already deal with this every year apple extends the Apis and there are various techniques to using the extended Apis and falling back to the old ones
Ah, now I get your point. Yeah, unfortunately you can be pretty sure that any interesting "extended API" would be a small wrapper around a windows-specific OS-provided service and thus unportable. That was the big issue with the MS Java extensions too I believe.
No, he is saying extended the iOS API - say to read from a heat sensor. Then it will only work on the windows/ios hybrid, not on the true iOS app.