[pjmlp]

Because most of the time we don't have a choice.

At work, I am yet to get a customer that allows us to use anything but Eclipse. At home I rather use Netbeans for Java projects.

For Android, the Android Studio barely supports the NDK. So we are left with the older Eclipse CDT plugins, Visual Studio or NVidia CodeWorks.

[dkopi]

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.

[pjmlp]

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.

[dkopi]

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.

[pjmlp]

If you look at my karma and post history you can easily find me.

I don't do trash talk, just tell my opinion as a hard truth and I stand by my opinion.

I learned through my life to stand by what I believe, without gaming up and down votes.

I would express the same opinion at Google IO, if given the opportunity to be there.