Until I can write Android apps in something else, yes. :)

Well, then you can unlearn Java right now!

http://xamarin.com/ http://phonegap.com/ http://www.orubase.com/ etc. etc. etc.

These frameworks are very limiting comparing to developing in Java. They might be easier to use (I don't know about that) but you would find yourself resorting to Java for the more complex stuff.

Can you come up with one thing that you can't do with Xamarin (C#) that you can do in Java (Android)? It's most certainly not 'very limited', I have no idea where you got that information.

You have the Xamarin extra payload and need to have someone write .NET bindings for the Android APIs.

But it is certainly a good way to write portable software across all mobile platforms.

This http://kotlin.jetbrains.org/ is the best language for Android development.

I think you should motivate 'best' :).

In general, Kotlin is a good candidate for the next Java. It removes a lot of boilerplate from Java and makes it more powerful (e.g. through extension methods), without becoming an enormous language such as Scala. It is a predictable language for anyone coming from Java.

Kotlin's largest competitor is Java itself. Java 8 does provide a lot of the advantages that Kotlin had (e.g. closures).

Java 8 unfortunately does not have closures

http://stackoverflow.com/questions/17204279/does-java-8-supp...

By that standard Haskell doesn't have closures either.

A closure is a function that uses free variables in its definition. And Java 8 closures fulfil that definition.

I agree with most of the things here except for the last part of no. 9:

"Beware of "I built an internal tool that..." or "I built a flux capaciting tool that..." or "I rewrote an open source tool because...". Some developers like to jerk off to rebuilding the wheel and wasting business money on projects that strictly aren't required or useful to the business as a whole. Like I said, I like to build products. If you feel like you needed to rewrite the compiler, you're probably awful, and almost certainly wrong."

What about DevOps and people who work on improving the work flow for other developers?

Otherwise, great list.