Interesting that Fuchsia isn't mentioned, being capability based and having a microkernel. Seems like there should have been a short explanation of why they didn't use it.
The Github page for Sparrow is counting RAM usage in megabytes with decimals, I don think Fuchsia will even run with less than 30MB of RAM. Their example for OOM events shows a device with 8GB of RAM, though I find it doubtful that even Google's hardware is that wasteful with system resources.
Though those small devices are getting pretty big hardware these days, since it's cheap now. Some of the Nest thermostats have 512MB of RAM, and 2GB in the higher end Home hubs.
Based on the function it serves I'm actually kind of appalled. It's a thermostat. You set the temperature and a schedule and it follows along. An ESP32 can do all the Wifi and Bluetooth connectivity you want with half a megabyte of RAM. Maybe you need a few megabytes for a framebuffer for the screen it has. But half a gigabyte?!
I had to look it up [1] and fact check this statement. Turns out it really is "megabytes with decimals". Amazing!
I'm not seeing mention of it on the initial website, so am guessing "no". :/
They don't own you anything, specially when they use it already in their products and just recently announced a new product with it [1], so you are just using FUD at this point
They mention: "Our team in Google Research"
They have multiple R&D teams so and they are working multiple projects
[1] - https://9to5google.com/2022/06/23/google-fuchsia-nest-hub-ma...
It's not unusual when announcing a new product to explain where it fits in with the rest of the products and why it was needed.
Didn't say that. Where did you get that quote, "they don't use it anymore" ?
I did say "why they didn't use it", meaning, "why didn't they use it for this specific use case?"