Jake Wharton, an Android developer, writes about Android, Kotlin, and library design.
HN links it for posts on Android and Kotlin topics, such as the testing robots pattern and removing Google as a single point of failure.
I don't think we've mellowed, just that we have become more sympathetic to Facebook's problem. I think the reality is that the 65k method limit problem has turned into something Android Developers put squarely at Google's feet. At the time I thought, what the hell is Facebook doing? Now, I've run into the 65k limit myself on an app written by 4 people over 18 months. Sure it's not a throwaway weekend project, but that is a pretty standard app.
Google either needs to blow away the 65k method limit, or figure out a way to make Google Play Services a lot lighter. As it stands right now, if you want just push notifications you are giving up ~20k methods of your 65k limit for that alone.
Just look at this post from Jake Wharton (leading Android open source developer): http://jakewharton.com/play-services-is-a-monolith/
Haven't watched it yet, but looks like the author gave a talk recently about differences between Kotlin and the latest Java: https://jakewharton.com/whats-new-in-java-19-the-end-of-kotlin/
Sounds like the Testing Robots Pattern which I first heard from Jake Wharton. Looks really nice
https://jakewharton.com/testing-robots/
Recent article I read from someone who works on Android: https://jakewharton.com/removing-google-as-a-single-point-of-failure/