Mac android emulator arm

broken image
broken image

I've been doing Android since 2011 and went through Eclipse, IntelliJ, then Android Studio and through various apps (from Starbucks, Ookla Speedtest, to smaller things like 8tracks online radio app). I get it that most users are 'happy with their 5 year old machine running two emulators and building big apps and having no issues with', but that's until you try the same in a newer machine, with faster CPU/GPU and more RAM (and possibly much faster IO), that you realize, wow, this is much snappier than before! Chrome is a monster (I use FFOX, and it's not much better), basically because web 'pages' became 'web apps' and well, everything uses RAM. I, too, worked with 8 and 16 gb for years I don't want memory to be an issue at all, now or in 3+ years (Which is roughly what a machine lasts these days, sometimes hopefully more).įrameworks keep getting bigger and demanding more memory, most apps are switching to hybrid approaches (React, Electron, etc.), which is a memory hog anywhere you look at. :) Java is a very demanding language, and IntelliJ as nice at it is, loves memory.