2 ms·

I imagine that as things stabilize Firefox will be able to handle it. After all, it needs to be manageable by the Chrome team too. Unless the Chrome team is giv

I imagine that as things stabilize Firefox will be able to handle it. After all, it needs to be manageable by the Chrome team too. Unless the Chrome team is given hidden notice about API changes well in advance, which seems sort of unlikely.

bagacrap 3y ago
Every time an API changes, whether by a little or a lot, the FF team has about 2 months to deal with it. You think that's going to happen? There's just a squad of engineers sitting around doing nothing at all times, waiting for the next emergency to drop? The amount of resources moz would need to allocate to this project (which has little purpose given alternatives) would be prohibitive.
- insanitybit 3y ago
  > Every time an API changes, whether by a little or a lot, the FF team has about 2 months to deal with it. You think that's going to happen? Yes? That doesn't sound that hard. Browser release on a tighter cadence than that. And it's just starting off at 2 months. > There's just a squad of engineers sitting around doing nothing at all times, waiting for the next emergency to drop? Uh... no? They would be normal FF engineers who would sometimes get a release ticket that says they need to update to a new API... > The amount of resources moz would need to allocate to this project (which has little purpose given alternatives) would be prohibitive. Totally disagree. This sounds like something engineers could take as a chore.
  - bagacrap 3y ago
    The fact that you think this sounds easy makes it apparent how little experience you have in this domain.
    - insanitybit 3y ago
      The domain of writing software against an API?