@oborosaur @PeterBronez I'm very interested in Fuchsia! My main complaint about it is: why not target some of the more community oriented hardware out there right now? Fuchsia on pine64 hardware for instance would be really interesting
Conversation
Notices
-
Christine Lemmer-Webber (cwebber@octodon.social)'s status on Tuesday, 20-Dec-2022 07:40:03 JST Christine Lemmer-Webber -
Oborosaur (oborosaur@hachyderm.io)'s status on Tuesday, 20-Dec-2022 07:40:04 JST Oborosaur @PeterBronez 3) I am watching @cwebber 's work with great interest.
I think "uniquely good" might be an over-sell, but there's a nice "turtles all the way down" aspect to running distributed capabilities on hosts that implement local primitives as capabilities. Nice uniformity.
OCap systems are only as safe as their underlying implementations are correct. It seems likely that bugs that could undercut cap properties would have "fewer places to hide" on a smaller cap-based kernel.
-
Oborosaur (oborosaur@hachyderm.io)'s status on Tuesday, 20-Dec-2022 07:40:05 JST Oborosaur @PeterBronez 2) I don't know.
-
Oborosaur (oborosaur@hachyderm.io)'s status on Tuesday, 20-Dec-2022 07:40:06 JST Oborosaur @PeterBronez 1) I would say that depends on your use case. Google uses #fuchsia in production on smart displays: https://www.theverge.com/2021/8/18/22630245/google-fuchsia-os-nest-hub-rollout-release-date
These devices are interesting because they need solid audio/video performance with constrained resources compared to, say, a laptop. On the other hand, they don't run as wide a variety of applications.
-