Comment by Sabinus
2 days ago
>The big problem is Google seems to have let the whole thing stagnate since like 2019.
Google's flightiness strikes again. How they expect developers (and to some degree consumers) to invest in their churning product lines is beyond me. What's the point in buying a Google product when there's a good chance Google will drop software support and any further development in 5 years or less?
At my last day job, https://github.com/google-coral/libedgetpu/issues/26 this was the last nail in the coffin that got us to move away from coral hardware. This was when we were willing to look past even the poor availability of the hardware during the peak chip shortage.
> As per https://www.tensorflow.org/guide/versions , Can we assume that libedgetpu released along with a tflite version is compatible with all the versions of tflite in the same major version?
> Hi, we can't give any guarantee that libedgetpu released along with a tflite version is compatible with all the versions of tflite in the same major version.
Yea, right! stares at my Nest smoke detectors
For a device with a 10 year life, and enough connectivity to be future-proof, Google has handled them poorly.
It's only a few weeks ago that they added support for them in the Home app.
I believe they have a 802.15.4 radio, maybe the x chipset is too old, but it would have been great to get Matter over Thread support for them.
New-comers like Aqara will instead take up that space.