Re:Android Needs A Simulator, Not An Emulator
by christop on Monday June 16, 2014 @04:13PM
(#7901211)
Genymotion is mentioned in the article, along with the reasons why it's not ideal (aside from the fact that it's not a first-party solution, and that you can't get a version with the Google SDKs running).
Re:Android Needs A Simulator, Not An Emulator
by nailer on Tuesday June 17, 2014 @09:48AM
(#7904362)
> You can't get a version with the Google SDKs running
Technically you can, it's just hard to do and should be there by default (I very much agree in spirit).
Re:Android Needs A Simulator, Not An Emulator
by recursive on Monday June 16, 2014 @05:01PM
(#7901452)
Wow, that page has a 2.5mb png as a background image on one of the elements.
Re:Android Needs A Simulator, Not An Emulator
by smrtinsert on Monday June 16, 2014 @07:16PM
(#7902023)
wow, how many jqueries is that?
Re:Android Needs A Simulator, Not An Emulator
by recursive on Monday June 16, 2014 @09:03PM
(#7902346)
80, counting gzipped jquery.
web 4.0
Re:Android Needs A Simulator, Not An Emulator
by yesimahuman on Monday June 16, 2014 @04:39PM
(#7901363)
It's mentioned in the article, but the downsides are almost all due to the licensing and pricing model. Doesn't really make it a bad solution from a technical standpoint (and for others to do something similar).
To me Genymotion is what Android "should" have, and it's already here.
Genymotion is the way to go. Google's emulator plain sucks.
Google should buy Genymotion!
http://www.genymotion.com/