So after the recent news that the Fuchsia team picked the Chrome OS-powered Google Pixelbook as a supported device, we jumped at the chance to get it up and running. And after a little elbow grease, it actually booted. Now, we’re not just running the system UI on top of Android like last time, we’re running Fuchsia directly on a piece of hardware!
This means it’s finally time for a deep dive on what Fuchsia looks like in early 2018. Our usual in-development OS testing caveats apply: Fuchsia only started development in 2016 and probably has several years of development time ahead of it. Everything can – and probably will – change between now and release (if a release ever even happens). Google won’t even officially acknowledge the OS exists – Fuchsia is a bunch of code sitting on fuchsia.googlesource.com.
This is quite exciting, and I’m definitely jealous I can’t justify buying a Pixelbook just for this. Not that I could – as with everything Google, it’s not available here.
Cool, but I’m really waiting to hear about how sophisticated and `deep` the user “telemetry” and data mining will be.
We might never know, because Fuchsia no longer requires anything (L)GPL related.
Using a GPL kernel and core utils never stopped people from being spied on by Google. Remember when the Debian folks noticed that Chromium (not even Chrome) was downloading blackbox binaries that listened in on your microhpone, even on Linux?
https://arstechnica.com/information-technology/2015/06/not-ok-google…
True enough. However, having the ability to ship a binary that can not be recreated from source, makes things easier for Google.
If you have to ask, you already know the answer.
I mean its google…
as with everything Google, it’s not available here
Same here (Brazil). Last available phone, if I can recall, was Nexus 5. OTOH, I can leave my desk now and come back in 30 min with an iPhone. Too bad.
Edited 2018-01-19 13:35 UTC