A Kernel Hacker Meets Fuchsia OS
I think the more interesting thing here is the fact that so much code in their repository appears to be bit-rotted or half baked, despite being documented. KASLR is mentioned all over the place but doesn&#x27;t work and the answer is &quot;we know, it&#x27;s there only to stop it bit-rotting&quot;. You need to patch the system to do kernel debugging because otherwise the toolchain hangs. Syscalls are documented as enforcing security rules yet the actual checks are &#x2F;&#x2F;TODO comments (and they are still willing to assign CVEs so apparently they just forgot?!). The syzcaller tool is advertised as working with Fuschia, yet despite trying multiple different versions he can&#x27;t even compile them due to API churn. Apparently downloading and executed a binary isn&#x27;t even an option, despite their vision being that Fuschia is a sea of components downloaded and run from the internet.<p>It&#x27;s hard not to feel like maybe Google has lost the ability to develop operating systems. Fuschia has been in development for years now, it has no users outside of Google yet if you flick through their docs you&#x27;ll notice a whole bunch of pages talking about deprecated components, migrations, etc. When I last looked at their docs, they read like it&#x27;s been around for 20 years and has millions of apps, even though that&#x27;s not true. Oh yeah and of course the giant BLM banners everywhere they have&#x2F;used to have. Just checked, now those banners are replaced with &quot;Honoring Asian Pacific American Heritage Month&quot;, lol. Apparently their vision of a futuristic OS is one in which every page in the docs has some random totally US centric bit of virtue signalling in it. No wonder they somehow can&#x27;t even finish a <i>microkernel</i>, a design that reduces performance in return for a much smaller syscall surface area.