It's less Linux because this is another step towards Chrome OS devices not running any Linux at all except for in niche situations, and in those cases only as a

It's less Linux because this is another step towards Chrome OS devices not running any Linux at all except for in niche situations, and in those cases only as a VM. The decision to use a VM is the telling part. If they were committed to Linux as the underlying kernel in Chrome OS this would just use process-level isolation like containers. When measured in terms of number of devices actually running a Linux kernel on physical hardware, in a post-Fuchsia Chrome OS world there will be less Linux kernels executing on devices at the bare metal, according to my prediction. Between this and Android pivoting to Fuchsia, the number of non-server devices executing Linux kernels on physical hardware will have dropped substantially. For anyone who values having a well-supported GPL kernel with maintained and modern hardware drivers as an option it should be viewed as incrementally more bad news. Microsoft and WSL is another facet of this attack on the Linux kernel. By providing a way to run a Linux userspace directly from existing proprietary Windows installs, they remove a bulk of the impetus a Windows user may have had to attempt running the Linux kernel directly on their physical hardware. We're headed towards a future where relatively few people run Linux at all directly on non-server hardware. Which enters into a self-reinforcing scenario of even fewer people doing so because the kernel development community will be working with fewer resources to keep up with hardware developments. I hope I'm wrong, but it's looking increasingly like the future of Linux-based clients will be IoT and raspberry pi like devices.