> But look at the timing.

Coincidentally, that was around the same time that Microsoft filed an Amicus brief supporting Oracle (in Oracle v. Google) arguing that APIs should be copyrightable[1].

Did that Project Astoria implement Android APIs? Would Google go after Microsoft in court had they officially released this? My guess is "yes" to both these questions. Nothing says wilful infringement louder than submitting a legal document to the courts spelling out why you think what you're doing (Astoria) is wrong.

1. http://www.groklaw.net/articlebasic.php?story=20130221153759...

I think you are wrong on the Google front. Google did everything to please devs. Take apple for example, they won't think twice about refusing your app. Google OTOH, since the early days, lacked so much in the Appstore, that they let all sort of trash inside. They just wanted the devs more than quality.

How many platforms does that Microsoft emulator work on? One? Unlike Microsoft, Google supports 3 development platforms and so their new emulator also had to support 3 platforms. Also, the new emulator was written from scratch and that takes time.

Well, Intel introduced HAXM a long time ago. It made it run quit faster.

It'd make sense if Hyper-V wasn't monopolistic. You can't run both at the same time, or better, no other virtualization host is allowed when Hyper-V is on. Which sucks.

I suggested an improvement and got back an email.

https://blog.rthand.com/post/2017/05/02/good-bye-visual-stud...