News for hackers. Stuff that matters.
Re:Leaving .Net by kenjackson on Wednesday December 15, 2010 @05:41PM (#2010136)
And embedded ARM processors outnumber desktop x86s by a large margin. I carry at least three of them with me at all times.

And Visual C++ targets ARM also, and has for years. One of the reasons I've heard bandied about as to why WP7 first party apps are so fast and responsive is because of the quality of the Visual C++ compiler. :-)

Re:Leaving .Net by rbanffy on Wednesday December 15, 2010 @09:15PM (#2010853)
None of the ARMs I carry with me run WinMo or had binaries compiled with VC++. The odds of WinMo devices outnumbering competing devices are very slim.

But you surprised me now: wasn't WP7 managed code-only? Has MS decided to allow native app code?

Re:Leaving .Net by kenjackson on Wednesday December 15, 2010 @09:52PM (#2010929)
Yes, the number of non MS-ARM devices is probably several of orders of magnitude more popular. But you'd be surprised at how many embedded devices run Windows CE.

Regarding WP7, 3rd party apps are managed. But the core OS is native and 1st party apps can be native. For example, IE and the mail app are both native C++ apps.

Honestly, I think allowing 3rd party native apps would be a mistake in general. Although I'd create a partners program where you require devs to pay $10k and then go through a certification process, which allows them to ship native apps. Basically its the XBox model. Indie devs use managed code. Apps that are willing to go through the more expensive process get native access.

Why? Native apps introduce a bunch of problems that are a pain to deal with. For example, there a bunch of security issues and stability issues that native apps introduce. Additionally you have to target native apps to an architecture. It may lock WP7 into ARM, due to the ecosystem, and block it from moving, for example, to a new Intel architecture.