<dev-planning-boun...@lists.mozilla.org>
To: dev-plann...@lists.mozilla.org <dev-plann...@lists.mozilla.org>
Sent: Mon May 19 16:15:45 2008
Subject: Re: What's next after Firefox 3 and Gecko 1.9?

I think we gained very little as far as add-on compatibility goes by
freezing as many APIs as we did. Only binary extensions have anything to
gain by the level of freezing that we used, script-only extensions will
not be affected.

I don't have any data on how many of our top-extensions have binary
components though.

The cost of freezing all interfaces was quite high. It uglified new code
a good bit as well as cost in performance and memory (though probably
not to a significant extent).

This was sort of ok when the changes went in to a branch that is
eventually going to die. It would suck a lot more to do that to
mozilla-central where we'd have to clean up the mess later, or live with
it forever.

/ Jonas

Mike Beltzner wrote:
> What would that answer mean for add-on compatibility?

> cheers,
> mike

> ----- Original Message -----
> From: dev-planning-boun...@lists.mozilla.org
> <dev-planning-boun...@lists.mozilla.org>
> To: dev-plann...@lists.mozilla.org <dev-plann...@lists.mozilla.org>
> Sent: Mon May 19 15:55:37 2008
> Subject: Re: What's next after Firefox 3 and Gecko 1.9?

> Q: Will *all* APIs remain compatible between 1.9.1 and 1.9 as they were
>     between 1.8.1 and 1.8?

> A: No, only frozen APIs will remain compatible. I.e. we are free to
>     change as many APIs between 1.9 and 1.9.1 as we did between 1.8 and
>     1.9

> At least that's what I'm hoping the answer is :)

> / Jonas
> _______________________________________________
> dev-planning mailing list
> dev-plann...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-planning
_______________________________________________
dev-planning mailing list
dev-plann...@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-planning