Linked by Thom Holwerda on Fri 11th Feb 2011 11:35 UTC
Thread beginning with comment 462055
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.
News
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
More News »
Sponsored Links



Member since:
2005-11-29
I like developing in Silverlight, very neat and great for thin web frontends. Good for customising the phone in any meaningful way? NO.
WP7 is not meant to be heavily customized. WP7 is meant to provide a consistent experience across a broad range of devices. This is why WP7 performs, looks, and feels the same across the 10 devices it launched on.
Find me 10 Android devices that do the same. Hell, find me 5. 2?
All native code does is pave the way for bugs, leaks, and performance losses. Managed code is the saving grace of the platform, and I for one hope that they never release a native SDK for general consumption.
I'd much rather them wrap native APIs in managed code and release them over time, than let people start dealing with raw pointers on WP7.
Furthermore, this was largely besides the point, I merely mentioned that OEMs get native SDK access, and that Nokia would have no trouble adapting its existing talent to WP7.