It makes sense if Fuchsia's main use cases are IoT devices, given how common public-facing vulnerable IoT devices made by defunct companies there are. It also m

It makes sense if Fuchsia's main use cases are IoT devices, given how common public-facing vulnerable IoT devices made by defunct companies there are. It also makes sense if Fuchsia eventually replaces Linux as the Android kernel, given the historical short EoLs and lack of security updates (see: https://androidvulnerabilities.org https://androidvulnerabilities.org). For a development machine, I'd honestly... be pretty fine with it. That's similar to how Arch Linux operates (but change hourly to daily or weekly) and it causes very few problems. I think I've had maybe two or three big issues caused by updates in the past year, plus a couple application-specific issues (not kernel-level or os-level). With a more extensive regression testing team I can see Fuchsia following through with the promise of seamless updates. Windows updates also have possibly the worst reputation you can get (except, maybe, iOS update's reputation when Apple was slowing down older devices), so almost anything Google does will be better. Not needing to reboot (presumably, if they're checking every hour) after an update will also help.