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

Post by fyrn_ » Sun, Jun 30, 2024, 4:26 AM UTC

SoftTalker wrote: post #14

kccqzy wrote: post #9

Earlier quoted context omitted.

I don't think so. Chrome is already the most popular browser. If a website decides to use this they are just going to tell users to use Chrome. And then Chrome sustains its dominant position. It's the right strategy for them to further their dominance. And the right way to think about it isn't other browsers. It's Google seeing what Apple is doing in iOS 18 and imitating that.

> It's the right strategy for them. That's what people said about Internet Explorer

Post by kevindamm » Sun, Jun 30, 2024, 4:40 AM UTC

mikeqq2024 wrote: post #69

oefrha wrote: post #35

See https://developer.chrome.com/docs/ai/built-in https://github.com/jeasonstudio/chrome-ai I can’t seem to find public documentation for the API with a cursory search, so https://github.com/jeasonstudio/chrome-ai/blob/ec9e334253713... might be the best documentation (other than directly inspecting the window.ai object in console) at the moment. It’s not really clear if the Gemini Nano here is Nano-1 (1.8B) or Nano-2…

1.8B/3.25B is still too much for edge devices. Ideally tens or hundreds mega would be ok. Is there an option to change the builtin Gemini Nano to other smaller models? By the way, haven't touch the lastest JS code for a while, what does this new syntax mean: "import { chromeai } " Also not get the textStream code: for await (const textPart of textStream) { result = textPart; } does result get override for each loop s…

Post by [deleted] » Sun, Jun 30, 2024, 4:59 AM UTC

kevindamm wrote: post #83

mikeqq2024 wrote: post #69

Earlier quoted context omitted.

1.8B/3.25B is still too much for edge devices. Ideally tens or hundreds mega would be ok. Is there an option to change the builtin Gemini Nano to other smaller models? By the way, haven't touch the lastest JS code for a while, what does this new syntax mean: "import { chromeai } " Also not get the textStream code: for await (const textPart of textStream) { result = textPart; } does result get override for each loop s…

`import { chromeai } from ...` is doing destructuring of the exported symbols of the module being imported. So, here it only imports the variable or type or function named chromeai.

Post by bpye » Sun, Jun 30, 2024, 5:06 AM UTC

fyrn_ wrote: post #80

flakiness wrote: post #73

So they don't standardize things anymore? Look at WebNN [1]. It's from Microsoft and is basically DirecttML but they at least pretend to make it a Web thing. The posture matters. Apple tried to expose Metal through WebGPU [2] then silent-abandoned it. But they had the posture, and other vendors picked it up and made it real. That won't happen to window.ai until they stop sleepwalking. [1] https://www.w3.org/TR/webnn/…

Don't have to when you they have achived a functionally total monopoloy

Post by jchw » Sun, Jun 30, 2024, 5:13 AM UTC

richardw wrote: post #79

onion2k wrote: post #36

My first impression is that this should enable approximately what Apple is doing with their AI strategy (local on-device first, then filling back to a first party API, and finally something like ChatGPT), but for web users. Having it native in the browser could be really positive for a lot of use cases depending on whether the local version can do things like RAG using locally stored data, and generate structured inf…

Apple might have an advantage given they’ll have custom hardware to drive it, and the ability to combine data from outside the browser with data inside it. But it’s an interesting idea.