More containers on Chrome OS
chromeunboxed.com
chromeunboxed.com
By definition then, solving the app gap by using a container to host Android or desktop Linux programs is non-native.
It is simply some extra properties in kernel data structures that allowing multiple views. But a container is just a process no different than any other.
The initial supposition was largely based on price and a larger SSD than normal without considering the obvious reasons.
The pixel Chromebooks have always been expensive, so no surprise there. Likewise, loads of people (myself included) refused to spend thousands if the most local storage was 64gb with a horribly slow USB 2.0 SD card reader for expansion. I remember reading (a Reddit IMA IIRC) that they wanted a larger drive, but couldn't because reasons.
I'm seriously considering getting one now that my biggest objections are gone and I'm sure I'm not the only one.
I love sandboxes, do not want to have random application X accessing my $HOME at its own pleasure.
The problem is they use a fake Chroot so somethings do not work. Here Google would use the KVM to soleve that issue.
BTW, Google does run all Android apps in a single container. Plus there is a weird issue where the IP is hardcoded in the container which if use the same IP elsewhere will cause issues.