←back to thread

Chrome is adding `window.ai` – a Gemini Nano AI model right inside the browser

(twitter.com)
229 points modinfo | 2 comments | 30 Jun 24 01:56 UTC | HN request time: 0.44s | source
Show context
SeanAnderson ◴[30 Jun 24 02:20 UTC] No.40834703[source]▶
This doesn't seem useful unless it's something standardized across browsers. Otherwise I'd still need to use a plugin to support safari, etc.

It seems like it could be nice for something like a bookmarklet or a one-off script, but I don't think it'll really reduce friction in engaging with Gemini for serious web apps.

replies(5): >>40834719 #>>40834754 #>>40834763 #>>40834819 #>>40834952 #
1. swatcoder ◴[30 Jun 24 02:37 UTC] No.40834763[source]▶
I'm sure you realize that Google's strategy has long been the opposite: that users will continue to abandon other engines when theirs is the only one that supports capabilities, until standards no longer matter at all and the entire browser ecosystem is theirs.

Chrome may have been a darling thing when it was young, but is now just a fresh take on Microsoft's Internet Explorer strategy. MS lost it's hold on the web because of regulatory action, and Google's just been trying to find a permissible road to that same opportunity.

replies(1): >>40836263 #
2. klabb3 ◴[30 Jun 24 10:14 UTC] No.40836263[source]▶
> users will continue to abandon other engines when theirs is the only one that supports capabilities

That’s why people chose chrome? Citation needed. I’ve very rarely seen websites rely on new browser specific capabilities, except for demos/showcases.

Didn’t Chrome slowly become popular using Google's own marketing channel, search? That’s what I thought.

> MS lost it's hold on the web because of regulatory action

Well, not only. They objectively made a worse product for decades and used their platform to push it, much more effectively than Google too. They are still pushing Edge hard, with darker patterns than Google imo.

In either case, the decision to adopt Chromium wasn’t forced. Microsoft clearly must have been aligned enough on the capability model to not deem it a large risk, and continued to push for Edge just as they did with IE.