Even if they didn't realize it, I don't believe they were arguing that firefox and chrome didn't/wouldn't use machine learning already, rather that they just thought the use cases you provided don't really sell the cost of having a full LLM integrated into every browser install.

This is exactly it.

  > the cost of having a full LLM integrated into every browser install

There's no fucking way there's going to be a "full LLM integrated into every browser." You really think they're going to drop in a 20GB-200GB model with every browser? Mind you, Llama-8B is over 15GB.

Nah. So far they are doing about 50MB per language translation that you ask for[0]. You have to explicitly install languages to translate.

There's neither "a full blown LLM" (whatever that means) nor forcing AI onto you. You still have to download the language packs, they are just offering an extension that more seamlessly integrates with the browser.

And we know what they're building too! Go look in the "Labs" tab and you'll see an opt-in for testing a semantic search of your history. That doesn't take an LLM to do, that takes a vector embedding model. What next? Semantic search in page? How terrible of a feature! (But seriously, can we get regex search?)

[0] https://hacks.mozilla.org/2022/06/neural-machine-translation...