You don't have to write Android apps in Java - that is just the normal way of doing it. You can write them in anything that is executed by native code including C, C++, C# (Mono) and there are many engines available including ones for Adobe Flash, Unity (C#) and even apportable.com which lets you use Objective C as has reimplemented the iOS APIs on Android. Google also have a SL4A that lets you use Python, or you could compile Python yourself.
If you want real pain, try doing Blackberry development, where you had no choice but Java, crappy APIs, overzealous procedures and crummy dev environment.
The hardest part of Android development isn't the code writing but user support - Android Market plays up, various devices you have never heard have quirks/bugs, feature support varies etc.
The swipe gesture is really cool until a bunch of apps also want to use swipe within the app. At that point, you get to play the fun game of trying to perform a swipe that is long enough to get the app to acknowledge it without starting at the edge of your screen, because that would cause the OS to switch out of the app.
There is no option to display 24-hour time and YMD other than by setting the locale. My phone now thinks that I am Japanese because I want it to display 24-hour time and YMD, but I do not know any Japanese, so every bit of software that localizes based on my locale is somewhat difficult to read.
It took a couple days to get IMAP IDLE to work, but even once it worked it would often repeatedly attempt to download a huge amount of email, fail midway through, and start again from the beginning rather than keeping whatever portion it had finished.
It is also missing a lot of software that two other OSes have, but I at least knew that would be true before buying it.
The fact that you hit numbers in the dialing screen and have to wait a few seconds before the phone makes any sound is another strong indicator that your phone is broken and you need to have it replaced under warranty. It is not supposed to be behaving like that.
I have not seen any swipe conflict between the applications and the phone's UI, which is basically because for the built-in gestures you swipe from the edges, whereas for the apps you swipe from inside the window. I don't see how you can get a conflict out of that. Can you give me an example of app that does that? Seem like an app fault, not phone fault.
Discussion of sexism has been very prominent on HN lately; I strongly suspect if that comment read "it's like the ugly wife that you want to divorce but can't afford to" then you would have got some kind of reaction. Perhaps we should remind ourselves that people with disabilities are worthy of the same kind of consideration and respect as everyone else.
Of course, but that was not the point of my post. It's Google who seems to be trying to distance itself from Android but can't, because they're in too deep.
Sorry, no offence meant.
Symbian and MeeGo are also getting constant OS updates although Nokia's official direction has shifted away to Windows Phone, and will continue like that for several years. As for Android, Google is treating it like an ugly retarded kid that they don't really want but are forced to take care of.