> - Needs a quadcore Xeon with at least 16 GB and SSD to have an usable experience with Android Studio, or configure it to run in laptop mode
I'd disagree with the Xeon bit, I have a 6 year old Sandy Bridge quad core, and Android Studio runs butter smooth.
I'll confess to the 16GB of RAM and an SSD though. Although honestly an SSD now days is required for anything to be usable.
Android Studio is amazingly performant though, the Emulator is great, ignoring bugs and glitches and the occasional times it just stops working until I flip enough settings back and forth that it starts working again.
Of course a huge benefit is that I don't need Apple hardware to develop for Android.
> I also rather develop for Android, but Android Studio resource requirements made me appreciate Eclipse again.
There is a reason my dev machine is a Desktop. Better keyboard, better monitor, better performance. 6 year old machine, cost about $1500, performs better than the ultraportables a lot of people try to press into service for writing code. Even with a faster CPU, thermal throttling is a concern once the form factor gets to a certain size.
Ah interesting, when my team used external consultants, we did the inverse, we gave the consulting company a beefy requirements list and told them anyone sent to work for us must be at least that well equipped.
Paying by the hour, we were heavily motivated to minimize compile times. :)
I'd disagree with the Xeon bit, I have a 6 year old Sandy Bridge quad core, and Android Studio runs butter smooth.
I'll confess to the 16GB of RAM and an SSD though. Although honestly an SSD now days is required for anything to be usable.
Android Studio is amazingly performant though, the Emulator is great, ignoring bugs and glitches and the occasional times it just stops working until I flip enough settings back and forth that it starts working again.
Of course a huge benefit is that I don't need Apple hardware to develop for Android.