A modern programming language that makes developers happier.

kotlinlang

I'm also on the fence about the implementation of the ViewModel providers, as they use a headless retained fragment for their storage mechanism, so that view models survive rotation.  I suppose this helps prevent leaks, but i'm wondering if there was another way they could go with it.  If android provided lifecycle mechanisms to know when an activity was being destroyed with the intention of recreating it, maybe another approach would work, but i'm not sure.