/s
The resources going into seL4 appear to be nowhere near "similar effort" to what Google is putting into Fuchsia, but it is a legitimate alternative.
Let's not be too quick to forget when Android first started out, all the idealism about the wonders of a free software mobile OS. A decade later, it's almost impossible to buy an Android phone that hasn't been strongarmed (no pun intended) into including Play Services, Chrome and Gmail, often including through threats to the manufacturer's unrelated businesses.
We're older and wiser, avoid this garbage like the plague, and don't fall for all the same old tricks.
Same with Fuchsia - its license should allow to make a fully FOSS privacy-respecting variant, and maybe it would be something I could recommend to my friends or family to replace Windows on their desktop for example (if Fuchsia becomes popular enough). At least such option exists, unlike in the case of Windows, so I don't see Fuchsia as a bad thing.
https://source.android.com/devices/architecture/modular-syst...
The information on the link is outdated, it was presented at Google IO that Android 12 will now also ship ART as APEX module.
Most likely by then the AOSP documentation will be accordingly updated.
I'm pretty sure that Play Services wasn't something Google really wanted to have but were forced to implement because so many OEMs just shit the bed w/r/t their Android forks.
[0]: https://genode.org/
The real community-driven alternative is Linux, which started and still is a monolithic kernel, but the multiple features it got along the years may make the distinction even less clear [2]. It seems it will also accept some Rust code in the future, so the difference may drop even in languages used. [3]
[1] https://www.gnu.org/software/hurd/
[2] https://qconlondon.com/system/files/presentation-slides/thom...
[3] https://lore.kernel.org/lkml/CANiq72khBa2GcB6-PHM3A44Y90d6vz...