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
 
Boris Zbarsky  
View profile  
 More options May 20 2008, 4:51 pm
Newsgroups: mozilla.dev.planning
From: Boris Zbarsky <bzbar...@mit.edu>
Date: Tue, 20 May 2008 15:51:01 -0500
Local: Tues, May 20 2008 4:51 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

Benjamin Smedberg wrote:
> I don't think we're optimizing for binary extensions, but rather for JS
> usage: the fewer JS extensions we break in this short cycle, the better
> off we are (of course, the same rule applies in general!)

I can pretty much guarantee that sicking was worried about things like
nsIContent and nsIDocument and nsPIDOMWindow, not about the very very few cases
in 1.8.1 where we created MOZILLA_1_8_BRANCH scriptable interfaces.

In general, doing an extra scriptable interface is less of a
footprint/peformance issue, and can be made completely transparent using
classinfo if needed...  It does take more work on the back end to do it that
way, of course.

In any case, binary extensions are the main reason we had a complete interface
freeze in 1.8.1, as I recall.  The question is how we want to handle them in 1.9.1.

-Boris


 
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