Post

In response to our objection to the Prompt API, some folks replied "well, fix it. Propose something better". This is something we end up doing a lot at Firefox…

…some of this is just part of participating in web platform design, but in some cases it's a little unbalanced. Given the same resources, I think we'd be in a better place if Chrome was working on fewer features, but fully-baking them. I don't think it's on Mozilla to fix every half-baked proposal.

Also, the lack of an alternative proposal is not a good reason to ship the half-baked thing.

Genuine question: are you happy with the role that the web plays on mobile devices today in comparison to native apps? If not, is it possible that the industry shift to AI might be an iPhone-level moment and put the web on the same position on desktop too (say, if openclaw and MCP takes on?)?

I would bet lurking in the background somewhere is a director or VP wringing their hands about adding more AI

“But we came up with something using our unlimited resources. Surely you can just make an effort now it’s announced and we’re pushing to resolve it”

standards are standards due to being deterministic (hence the word standard), and while some approaches (like translation) can be coerced into that standard, llms seem far too chaotic for me to imagine there is a way to integrate them, the prompt api is probably better as a library rather than

The web is a good 15 years behind native platforms. "Going slow" is just a recipe to become even farther behind, and failing users in the process. I remember the B2G days, and Mozilla's position was not to go slow then. I missing that Mozilla.

Do native platforms have first class prompt APIs?