I get the remark, it's certainly an interesting line of thought. In a way, this model reminds me of Ubuntu Core [0], although Ubuntu Core is more freedom lovin

I get the remark, it's certainly an interesting line of thought. In a way, this model reminds me of Ubuntu Core [0], although Ubuntu Core is more freedom loving than Android, but that is not your point obviously. Somehow I feel uncomfortable with the suggestions you make, but I find it hard to articulate. Somehow this does not sound like an attractive model, it sounds very "involved". Let me try to articulate why. I think a lot of the Android tooling sound new-ish, but actually I find it to be old-world in the server space. We have been moving more and more into declarative infra-as-code paradigms: Spin up a multitude of servers from a single text file that declares the final state of the entire architecture. Think Docker compose, Kubernetes/Terraform, Ansible, Chef/Puppet, Nix(OS). In a world where your servers/configs live in Git, where is the advantage for something as involved as Android, which in the end is just a Linux kernel with some APIs on top (and a privacy invading proprietary layer, again, not your point I guess)? [0] https://ubuntu.com/core https://ubuntu.com/core