yes, quite a bit of lifecycle discussion. It's my goal to have pure-compose activities handle their own config changes, i.e. not tear down and recreate the activity. With a reactive system it's redundant. In many ways you can think of Android's activity recreation as a very coarse-grained reactive rebuild of a UI and compose can do it granularly.