Google Fuchsia OS team affected by layoffs

Re:Google Fuchsia OS team affected by layoffs by justapassenger on Sunday January 22, 2023 @06:17PM (#34483417)

Hubs are fully vendor locked in, and Google controls every single but running there. Security argument, while valid like everywhere, seems BS. I’d be surprised if security profile for a hub was main concern for the product.

Anecdotally my hub got much less responsive around the Fuchsia update. I’m not blaming Fuchsia directly for it, but one could wonder what would happen, if resources dedicated to that, were spent on usability improvements.

Let’s be honest, Fuchsia was rolled to a Hub, because it’s a product no one really cares about and team needed some guinea pig/stuff in production to justify its existence. I say that confidently, as someone working at big tech, and having myself experience being in rollouts like that.

[ Parent | on HN ]

Re:Google Fuchsia OS team affected by layoffs by raggi on Tuesday January 24, 2023 @01:10PM (#34507484)

The Nest team definitely won't agree with your value judgement of these devices, nor do many of the users who paid for them. To this end, even if there are different motivations for different teams and other tactical considerations, it is absolutely necessary for the owning team of a product to have a real motivation for such a significant operation as replacing the entire firmware and runtime in the field. That set of motivations are rooted in the properties of the OS: https://fuchsia.dev/fuchsia-src/concepts

[ Parent | on HN ]