I'm always surprised at how many people willingly put up with Eclipse's clunkiness and performance problems, regardless of how many functions it provides.
Really ? I feel the exact opposite. Eclipse performs much, much better than Android Studio. Just having AS open is enough to kill any and all performance on my laptop, not just AS itself but the whole machine crawls. I have no issues with having shitloads of other software running the only thing that has such a dramatic impact is Android Studio.
It's not even using that many CPU cycles according to Activity Monitor but it slows down everything regardless. It seems to always be doing some bullshit, indexing or whatever even if it's just open in the background.
I'm running this on the latest model MBPro which has a super fast SSD and 16GB RAM. I usually have at least one Eclipse instance running with a Glassfish server. Also, Postgresql, Safari with 100-150 tabs open, countless text editors I use for not taking, usuually I have some graphics editors open too (Affinity Designer and Pixelmator), Chrome with a few tabs and Postman, Wireshark, Mail, Calendar, etc.
All this while driving a 4k screen in simulated-2560x1440 'scaled' mode (so it's basically rendering at twice that and scaling it down to 4k). All that runs smooth as butter. The only thing that seems to be able to get this machine on it's knees is Android Studio, no matter what I do. The only thing that seems to improve things a little is AS's power save mode.
NDK work accounts for a small percentage of android work.
If you're more comfortable with NDK on eclipse, that doesn't mean you can't build your ELFs in eclipse, and the rest of your project in Android Studio.
Looking for the amount of APKs that have at least one .so in them, the reality speaks otherwise.
Also that is a very lame excuse for the cold reality, that in spite of the very complex hiring standards of Google, they aren't able to write an IDE that offers an overall experience for their own platform.
Having an .so in your app doesn't mean the majority of work in your app is NDK work.
And it's often limited to just one or two team members while the rest are working on the java side of the app.
You also don't need the NDK at all to include an .so in your app. You only need the NDK to build the .so.
When it comes to regular android java work (which is the fair share of android development, as google obviously knows from anonymous statistics) - Android Studio takes eclipse hands down.
As for the google rant, I'm not a google employee, but I think their work has been amazing. Are there improvements I'd like to see? of course. But I've never understood how easy it is for people to trash talk the work of others given an anonymous nickname online.
It's not even using that many CPU cycles according to Activity Monitor but it slows down everything regardless. It seems to always be doing some bullshit, indexing or whatever even if it's just open in the background.
I'm running this on the latest model MBPro which has a super fast SSD and 16GB RAM. I usually have at least one Eclipse instance running with a Glassfish server. Also, Postgresql, Safari with 100-150 tabs open, countless text editors I use for not taking, usuually I have some graphics editors open too (Affinity Designer and Pixelmator), Chrome with a few tabs and Postman, Wireshark, Mail, Calendar, etc.
All this while driving a 4k screen in simulated-2560x1440 'scaled' mode (so it's basically rendering at twice that and scaling it down to 4k). All that runs smooth as butter. The only thing that seems to be able to get this machine on it's knees is Android Studio, no matter what I do. The only thing that seems to improve things a little is AS's power save mode.