I had no idea finding Android Developers was considered difficult. I started developing Apps with Android and always found it to be very straightforward. Java is much easier to understand than objective-c.
I've also never understood why Android is hated on as far as profits go. Sure nobody wants to buy anything, but (in my experience) ad eCPMs are comparable.
I agree with cliveowen (you da bomb in Children of Men, yo!) in that the language isn't everything. But for different reasons.
The Android documentation is spectacularly good, IMO, though admittedly it is more reference focused than tutorial focused (which works for me, YMMV). Eclipse sucks but Android Studio is pretty nice, and in either case you don't need to use an IDE if you don't want to. I use Sublime Text 2 and command-line builds most of the time, using Android Studio only when I want to do on-device visual debugging.
The Java thing is a bit more true, the language can feel somewhat painful at times, especially since it is frozen in time at Java 6 for the most part, with a few little bits of Java 7 thrown in at random with little to no clear guidance from Google on where it is headed post-Oracle lawsuit.
Also there are places where the OS APIs are a bit too Java-esque in terms of being overly abstracted without a compelling reason why. Also the whole activity/fragment lifecycle and the way services work is a bit weird at first for people used to writing traditional apps, but any competent developer will learn to live with it pretty quickly. It still tends to be a sticking issue anyway because of the fact that a lot of designers (who are mostly iOS-centric, as the original article alludes to) don't really "get it" and thus design in ways that don't fit the OS app lifecycle (and don't get me started on their "pixel perfect" designs).
All that aside I had no idea Android Developers were seen as hard to find. Maybe I need a raise!
The language isn't everything, in fact, it's the least important part of the package. Android has horrible online documentation, iOS has stacks of nicely formatted PDFs and a great online reference. Android tools (Eclipse/Android Studio) are simply horrible, while XCode and related tools are really great. Add to this the performance hit you have from having your code run on a vm and the bloat that comes from using Java itself, and you have yet another reason as to why Android developers are few and far between.
I'll take Android Studio over Xcode any day of the week. I've been working with the Xcode 6 GM for the last few days and it crashes hard on me at least once an hour. I think Android Studio, despite being in beta status, has crashed on me once in the entire time I've been using it. And Xcode's refactoring and code management tools are a joke compared to Android Studio's.
And I'll take Android's layout schemes over managing the house of cards that is auto layout in Interface Builder. If you're lucky you can get auto layout to do what you want with a ton of pointing and clicking but good luck maintaining that mess when you come back to it a few weeks from now. WYSIWYG tools have no place in a professional developer's toolkit, IMO. Leave that stuff to the designers.
Merging xibs and Xcode project files is another hell lying in wait for anybody doing Mac or iOS development on a team.
I'll grant you that the iOS documentation is generally better and certainly the APIs for dealing with multimedia on a lower level are far better on iOS. But for the typical listview-hitting-a-json-api kind of app life is generally easier in Android, in my experience.
I've also never understood why Android is hated on as far as profits go. Sure nobody wants to buy anything, but (in my experience) ad eCPMs are comparable.