News for hackers. Stuff that matters.
Re:Neither Microsoft, Nokia, nor anyone else should fork And... by rbanffy on Saturday February 08, 2014 @10:52AM (#7201457)
Microsoft could build a fully functional Mono-based Windows Phone experience on top of the AOSP core minus the Dalvik VM.

The only question would be "what for"? They'd gain nothing from it. They already have a more or less portable kernel upon which they can build phones.

Re:Neither Microsoft, Nokia, nor anyone else should fork And... by ahomescu1 on Saturday February 08, 2014 @06:47PM (#7203454)
It sounds to me like what they need is exactly the other way around: Dalvik VM + all the Java APIs in Android, on top of the WP kernel (or they could go with Linux, but I think the kernel doesn't matter as much).
Re:Neither Microsoft, Nokia, nor anyone else should fork And... by Maarten88 on Saturday February 08, 2014 @08:14PM (#7203743)
This.

But there is one problem with that strategy: if Microsoft would support running Android apps on Windows Phone, there would be little incentive left to write native WP apps. Everybody would only write for Android, making it hard to differentiate the platform.

Re:Neither Microsoft, Nokia, nor anyone else should fork And... by contextfree on Saturday February 08, 2014 @11:41PM (#7204404)
I wonder if it would be feasible to support Java and maybe some (most? some well-defined base of?) Android APIs in "native" Windows apps, in a similar way to how JavaScript and HTML are supported via WinRT's notion of language projections. Although this would mean narrowing the goal from "making Android apps run on Windows" to "making Android apps easier to port to and maintain on Windows".
Re:Neither Microsoft, Nokia, nor anyone else should fork And... by pjmlp on Saturday February 08, 2014 @11:55AM (#7201691)
Besides, since the Visual 2013 launch event, Xamarin has become an official Microsoft partner.