5 ms·

I suspect "stability" will look a lot different from Windows though. They won't be supporting old versions of the API for 30 years but maybe 3 months, since bot

I suspect "stability" will look a lot different from Windows though. They won't be supporting old versions of the API for 30 years but maybe 3 months, since both browser and OS are still expected to be kept up to date for security reasons and supporting old versions of code is onerous. Edit: found this - > The API boundary initially will be semi-stable: it will tolerate 1-2 milestones of version skew. We may allow larger amounts of skew in the future. FF would have a hard time keeping up I think.

insanitybit 3y ago
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?

insanitybit 3y ago

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?