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
 
Mike Shaver  
View profile  
 More options May 20 2008, 12:40 pm
Newsgroups: mozilla.dev.planning
From: "Mike Shaver" <mike.sha...@gmail.com>
Date: Tue, 20 May 2008 12:40:47 -0400
Local: Tues, May 20 2008 12:40 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

On Mon, May 19, 2008 at 7:15 PM, Jonas Sicking <jo...@sicking.cc> wrote:
> Only binary extensions have anything to
> gain by the level of freezing that we used, script-only extensions will
> not be affected.

As you've proposed, non-additive changes to unfrozen APIs can and will
break script-only extensions.  We broke a lot of script-only
extensions in 1.9, and we will have a much shorter "get your stuff
up-to-date" cycle than we had for 1.9.

I don't think we should freeze any more APIs, since I agree that it
has not paid for itself (and has led us to premature enfreezification
on APIs that nobody wants to use), but I don't think that we should
leap from that position to one of total API abandon.

We should _break_ as few APIs as possible, but no fewer.  Additive
changes to unfrozen APIs should be looked at with a kind eye, and more
disruptive changes should come alongside a case for why the API break
is significantly better than an additional new API or such clumsier
alternative.

Mike


 
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