Linked by Thom Holwerda on Fri 11th Feb 2011 11:35 UTC
Thread beginning with comment 461987
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
And why would MS allow them to port Qt?
[..]
Which also shows how much "influence" Nokia is going to get over direction of WP7.
[..]
Which also shows how much "influence" Nokia is going to get over direction of WP7.
I did not say MS would want to do it. Do not put words in people's mouth.. or hand, in the Internet case.
I said Nokia should have had this part of the deal, for it to be an OK deal.
This is Nokia's own fault here. If they cannot due to Microsoft, then it makes the alliance a bad move for developers, both code wise and trust wise. But especially trust wise I guess.
Simple.
Which also shows how much "influence" Nokia is going to get over direction of WP7.
Exactly!
After having told all their partners to invest time and money (for training, etc) into Qt, this would have been their most important influence on WP7.
I wouldn't be surprised if killing Nokia's developer ecosystem wasn't part of the things Microsoft wanted.




Member since:
2010-02-08
And why would MS allow them to port Qt? They want developers to use only .Net, Silverlight and XNA. Sure, MS cares about interoperability but only within their own walled garden - WP7, desktop windows, Zune, Xbox. Allowing Qt would be step in opposite direction, so it is not going to happen. Which also shows how much "influence" Nokia is going to get over direction of WP7.