Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
mozilla.dev.planning
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Message from discussion What's next after Firefox 3 and Gecko 1.9?
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Jonas Sicking  
View profile  
 More options May 19 2008, 7:30 pm
Newsgroups: mozilla.dev.planning
From: Jonas Sicking <jo...@sicking.cc>
Date: Mon, 19 May 2008 16:30:03 -0700
Local: Mon, May 19 2008 7:30 pm
Subject: Re: What's next after Firefox 3 and Gecko 1.9?
Print | View thread | Show original | Report this message | Find messages by this author
Yes, compat would definitely be affected. But I believe the benefit/cost
ratio is low enough that it's not worth it.

/ Jonas

Mike Beltzner wrote:
> Heh, so it would mean compat would be affected, then :)

> I'm not saying we should or shouldn't feeze. APIs, and most definitely we
> should make the decision based on previous experience. Just wanted to make
> sure I understood the impact.

> 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 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


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2012 Google