Agree. I was expecting the author to lament on something like java vs swift. Even that would not be the best argument ever since you can write your android

Agree. I was expecting the author to lament on something like java vs swift. Even that would not be the best argument ever since you can write your android apps entirely in kotlin and it is vastly similar to swift. A real downside of kotlin is that it complexifies your build (but only the first time you have to setup a complex project with kotlin, dagger, databinding, etc) and that the tooling is not on par with the base java one. Multidex ? it is far from perfect but it is not a day to day issue. I work on a 200k methods app and multidex actually makes it almost entirely painless. Gradle ? Nobody can seriously say that builds have gotten worse with gradle. Before it, we had no way to hook up libraries with resources (aar). Now we just have to 'import libname:version' The complaint on the build times is very fair though. The solution is easy though .. just use an high end computer I use a mid 2015 mbp, it can handle an huge android app without any issue (except that build times are only acceptable, not great). It really looks like he has been submerged with having 2 platforms to learn at once and has not been able to tackle the basics.