Notices by Oborosaur (oborosaur@hachyderm.io)

@cwebber @PeterBronez interesting idea! Unfortunately, I don't have a strong sense for how straightforward (or painful) hardware bring-up for fuchsia is these days, so it's hard for me to gauge whether the timing is right to try something like that.

I'm tired of scolling through posts about the birdsite.

I've been contributing to #fuchsia for a while now. AMA.

@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.

@PeterBronez 2) I don't know.

@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.