I wonder if it makes sense for browser vendors to agree upon and ship various ‘standard models’ that are released into the public domain or something, and the API lets you pick between them. The models themselves would be standardized and the weights and everything should be identical between browsers. They’d be standard and ‘web-safe’ like CSS colors or fonts. Probably would help to give them really boring/unbranded…
Mozilla's opposition to Chrome's Prompt API
11–20 of 248 posts
Re: Mozilla's opposition to Chrome's Prompt API
#12Re: Mozilla's opposition to Chrome's Prompt API
#13> This will result in Mozilla and Apple having to licence Google's model, or ship a model that's quirks-compatible with the Google model in order to be interoperable. It may also become difficult for Chrome to update its own model for the same reasons. Google is again doing Evil. I am very annoyed that Google kind of de-facto controls the www (through chrome, let's be honest here). We really need to change this. I do…
Re: Mozilla's opposition to Chrome's Prompt API
#14I wonder if it makes sense for browser vendors to agree upon and ship various ‘standard models’ that are released into the public domain or something, and the API lets you pick between them. The models themselves would be standardized and the weights and everything should be identical between browsers. They’d be standard and ‘web-safe’ like CSS colors or fonts. Probably would help to give them really boring/unbranded…
Not to mention many other UX questions the come with this, most importantly, how unusable these local models are on regular 3-year old laptops that are constrained in RAM, GPU/CPU capability and likely disk space despite what enthusiasts say here. (They have a Macbook Pro with 32+GB of RAM, reports it works great with xyz model -- fine -- but somehow thinks it works for everyone and local models are the future.)
Re: Mozilla's opposition to Chrome's Prompt API
#15> This will result in Mozilla and Apple having to licence Google's model, or ship a model that's quirks-compatible with the Google model in order to be interoperable. It may also become difficult for Chrome to update its own model for the same reasons. Google is again doing Evil. I am very annoyed that Google kind of de-facto controls the www (through chrome, let's be honest here). We really need to change this. I do…
Only have yourselves to blame. Chrome made the internet better but everyone put their fingers in their ears about it getting worse at the same time.
Re: Mozilla's opposition to Chrome's Prompt API
#16I wonder if it makes sense for browser vendors to agree upon and ship various ‘standard models’ that are released into the public domain or something, and the API lets you pick between them. The models themselves would be standardized and the weights and everything should be identical between browsers. They’d be standard and ‘web-safe’ like CSS colors or fonts. Probably would help to give them really boring/unbranded…
It doesn't make sense at all. So as a user how do you choose which model to use? There could be 3824 models to choose from. The browser might as well set one as default, and we all know how that goes (see: search engine). Not to mention many other UX questions the come with this, most importantly, how unusable these local models are on regular 3-year old laptops that are constrained in RAM, GPU/CPU capability and lik…
The model is pretty slow on my M4 Pro mac.
The API allows the browser to use a cloud service instead, but then privacy is lower. So, more privacy for the rich.
Re: Mozilla's opposition to Chrome's Prompt API
#17> Browsers and operating systems are increasingly expected to gain access to language models.[0] Are they? [0] https://github.com/webmachinelearning/prompt-api/blob/main/R...
Operating Systems: Windows (built-in Copilot), MacOS, iOS (Apple Intelligence)
So it's >90% desktop browser and OS, plus >30% mobile OS.
Yes, I think it's very safe to say "browsers and operating systems are increasingly expected to gain access to language models."
Re: Mozilla's opposition to Chrome's Prompt API
#18> Browsers and operating systems are increasingly expected to gain access to language models.[0] Are they? [0] https://github.com/webmachinelearning/prompt-api/blob/main/R...
So they should provide an interface to LLMs, disabled by default, enabled when users want it, and that’s it imho.
That also gives me the choice of which LLM provider to use, rather than being locked in whatever LLM Apple decided to do put in their OS.
I want to give Claude access to the stuff Apple Intelligence has access to, for example.
Re: Mozilla's opposition to Chrome's Prompt API
#19> This will result in Mozilla and Apple having to licence Google's model, or ship a model that's quirks-compatible with the Google model in order to be interoperable. It may also become difficult for Chrome to update its own model for the same reasons. Google is again doing Evil. I am very annoyed that Google kind of de-facto controls the www (through chrome, let's be honest here). We really need to change this. I do…
Re: Mozilla's opposition to Chrome's Prompt API
#20> This will result in Mozilla and Apple having to licence Google's model, or ship a model that's quirks-compatible with the Google model in order to be interoperable. It may also become difficult for Chrome to update its own model for the same reasons. Google is again doing Evil. I am very annoyed that Google kind of de-facto controls the www (through chrome, let's be honest here). We really need to change this. I do…
Only have yourselves to blame. Chrome made the internet better but everyone put their fingers in their ears about it getting worse at the same time.