Shooti

The difference is ChatGPT Pro/Plus plans have one shared pool of token limits shared across all use cases.

In contrast Google's AI plans give you at least three seperate pools of token usage limits: Gemini App + Antigravity/Other Code Assist tools like Android Studio + AI Studio free usage limits.

Google limit the context of where you can use their tokens but in exchange they give you substantially more.

> o changes are being made to the .tflite file extension or format. Conversion tools will continue to output .tflite flatbuffer files, and .tflite files will be readable by LiteRT.

Odd choice since it strongly undermines the stated purpose of the rebrand in the first place: to break it away from the Tensorflow brand and emphasise it being model/framework agnostic. Working with ".tflite" files more or less immortalises what they're trying to get away from.

Would've made more sense to bite the bullet and launch with a ".litert" format which is identical to ".tflite", but continue to work with the later. That would remove the conceptual integrity issue without breaking any compatibility.

They'll probably continue to co-exist: Flutter is a Declarative UI product by the Dart team, Jetpack Compose is a Declarative UI product by the Android org. Google has no problem having multiple competing products by different orgs unless one org manages to absorb the other.

Dart has survived this long so that doesn't seem on the cards.

Due to Mark Gurmans track record a Bloomberg rumor on a tech companies future plans for a product are almost as trustworthy as official PR from the company. More leaks = more representation on HN.

There is/was no such thing as an assistant called "Google Now". That was an illusion/poor branding.

There's "Voice Search", typing into the Google search box with your voice.

VS Assistant, a Google's chatbot interface.

>No HomeKit integration, of course, now that Google has purchased them.

Probably completely unrelated since Nest doesn't even support Google's Brillo/Weave. They're going forward with their own "Nest Weave" which despite the name is a completely separate platform/ecosystem from Google's stuff.

Wouldn't be surprised if Homekit support is actually on the cards but it's stuck in their super slow release cycle.

>I don't get it... Google clearly has more than enough in house talent to get those things right. Why aren't they? Why don't they seem to care?

I think it's because "Google" aren't involved at all. Google has it's own approach to IOT called Brillo/Weave that they're focused on. Nest is doing its own isolated thing.

They killed that a couple of months ago.

You can shop via an in-app browser within their Kindle app.