Tempest1981 20 hours ago

Forcing everything into a plug-in is architecturally more complex, and less performant... I'm imagining proxying from native code through JavaScript APIs, then back to native code for LLM operations and context storage. But might lead to creation of some new AI extension APIs.

▲

999900000999 20 hours ago | parent [-]

Then ship a FireFoxAI browser for users who want it.

Forcing everyone to by default use AI isn't freedom. I might as well just use Chrome.

▲

prmoustache 10 hours ago | parent | next [-]

Is it using AI if you don't click on the feature's related button? AFAIK when I choose to translate a page or a selection it only starts working when I do it.

▲

Tempest1981 19 hours ago | parent | prev [-]

So now we're debating compile-time feature flags vs run-time, and the overhead of running/maintaining multiple build configs. And picking good names for each... "Firefox Pro with AI" vs "Firefox Lite for Engineers". This isn't what Mozilla needs to be focusing on right now, imo.

	▲	999900000999 15 hours ago \| parent [-]
		With over 600 million in revenue they can afford to put up a different page for Firefox AI. A large percentage of users, particularly Firefox users , don't want this AI stuff built in. Where does this AI even run. Does it have to make an API requests to send all of the webpages I view somewhere else ? Is it even my computer anymore, my browser, or am I sharing it with people who want to extract more money from me. As is Google forced me to view often incorrect AI summaries when I have no interest in them. Do I want the only real Chrome competitor to also force bad ai content in my face ?