According to documentation, ( https://fuchsia-review.googlesource.com/c/docs/+/101356/4/fuchsia_paver.md#17 ), Fuchsia has decent hardware support for the Acer Switch 12, Intel NUC, and the recently released Pixelbook.
Hopefully, some decent and legacy free code will emerge from the Fuchsia project with some direct/indirect benefit to Haiku.
More information about Fuchsia you can find on the Fuchsia Wiki
https://fuchsia.miraheze.org/wiki/Main_Page
I think for all here, the kernel of it is most important.
Attila SzĂĄsz & GergĆ HosszĂș have analysed the Fuchsia kernel at
The latest try (of non google developer) to install a complete Fuchsia on real hardware (in this case on an pixelbook) you can see at
Greatings
theuserbl
Next week they âmayâ make an official introduction at the Development ConferenceâŠ
Google plant das neue Betriebssystem "Fuchsia"
Vielleicht wird es auf einer Entwicklerkonferenz schon nÀchste Woche offiziell vorgestellt.
Well, some years ago, haiku went to Googleâs summer of code, perhaps there was born the interest on be os and their engineers, as b plan, and now, fuchsia is a reimplementation of BeOSâ ideas but property of Google.
We had Haiku contributors working at Google long before Google Summer of Code was a thing. Including geist, who is currently part of the Fuchsia team and also a former Be employee.
I didnât know; thank you for the clarification 
If I remember correctly, the starting point for the current Haiku kernel was the NewOS kernel developed by geist (Travis Geiselbrecht).
While BeOS never became a commercial success on its own, its underlying design concepts and features live on.
Interesting article in that it brings bits of information about Fuchsia from a business/investor perspective rather than a technological perspective.
Some oversights though. There is no mention of the Pixelbook which is the first mass-marketed Google designed chromebook. The two previous Pixel chromebooks were limited edition high end (and high prices) devices. Also, the Pixelbook can run Fuchsia today albeit through a convoluted installation path.
Fuchsia is presented as a project to design a legacy-free kernel/operating system while incorporating the insights gained from the birth and evolution of Android and ChromeOS.
This goal is similar to that which was originally pursued with BeOS and it is good that some of its developers are ex-Be employees.
Much is said about the risks associated with breaking away from the current Android and ChromeOS ecosystems. However, Google has already demonstrated the viability of an intermediary layer to run Android applications within ChromeOS. And, in a very simplistic view, ChromeOS is the Chrome browser code compiled with a customized Linux kernel into a single image. Since the Chrome browser code is concurrently developed for multiple operating systems, adding one more (Fuchsia) should not be that difficult.
I believe that the intent is more than a senior-engineer retention project as the last sentence of the article would allude to. Will have to wait and see how the story develops.