I mean the whole motivation for Google to sink money into Fuchsia is not to diversify into the embedded space it is obvious they want full vertical control from the Zircon Kernel all the way up to user space.
A lot harder to degoogle if your device is nothing but google...
> they want full vertical control from the Zircon Kernel all the way up to user space.
Of course, I have been saying that for years.
Contrary to the 'Fuchsia is only an experiment', 'Fuchsia is going to be shut down' coping crowd, in fact, Google has been much further than once thought with developing Fuchsia and it is going to start with replacing Linux with Zircon in ChromeOS next, probably in 3 to 4 years.
Also explains why they already have the Chrome browser running in Fuchsia. So there is no doubt that they are intending to use Zircon in ChromeOS.
I think that makes sense too, and don't think that kind of "control" is necessarily bad. I've often written "dependencies" myself even though existing solutions exist so I have (full) control over them, and can do exactly what I want with them. I was reading an interview with SQLite creator Richard Hipp the other day, and he said pretty much exactly the same. It gives a lot of freedom.
That is the hard truth and the reality of it all and what is most likely going to happen.