Adblock Plus roadmap · 2009-12-03 11:11 by Wladimir Palant

I understand that the decision making process around Adblock Plus hasn’t been very transparent, particularly when it comes to questions like “what will go into that release” or “when is this release done”. I decided to put up a roadmap that lists the features being considered for future releases (at least the ones where the details have been worked out enough to be implemented). I’ll try to keep this list up to date and it is open for discussion of course (preferably in the forum). Releases generally happen when all features have been implemented (or moved out to future releases) and sufficiently tested in development builds (meaning at least a week of testing). This is where the tentative release date for Adblock Plus 1.1.2 comes from — with all features being done it is going to be released at the end of the testing phase if no issues come up.


Comment [4]

  1. tiik · 2009-12-04 01:50 · #

    I hope ABP can be more efficient(clean up code) and support mozilla jetpack

    Reply from Wladimir Palant:

    ABP is already pretty efficient – there isn’t much room for improvement (I added one performance-related bullet point but there isn’t much else I can think of). As to Jetpack – Jetpack has to support Adblock Plus, not the other way around. As it is now, Jetpack isn’t suitable for complicated extensions.

  2. Erunno · 2009-12-06 12:16 · #

    Since JIT will be enabled for chrome in 3.6 I would like to ask the following questions:

    1. Does “chrome” also include extensions?
    2. If yes, does ABP benefit from JIT compiling in any way in 3.6? What’s the difference in performance? And if JIT compiling does not speed up ABP, do you have any idea why?
    3. Will rewriting the core classes not make ABP more likely to crash Firefox in case errors slip in?

    Reply from Wladimir Palant:

    1. Yes.
    2. The existing performance tests say: no. JIT is meant to speed up code that runs for a long time, ABP (and most of chrome) doesn’t have such code. Instead there is code that runs very frequently. I’ll probably add more performance tests in future to see whether JIT influences the performance in other areas.
    3. Yes, this has been a major concern of mine. However, I think that crashes can be avoided if some coding guidelines are followed consistently. Anyway, there is a reason that this change isn’t scheduled – getting this right will take time.

  3. Enliq · 2009-12-10 19:22 · #

    Do you plan to develop a version for Google Chrome?

  4. Paul · 2010-01-04 22:41 · #

    is ABP available or going to be available for google chrome ?

    Reply from Wladimir Palant:

    Short answer: No
    Long answer:

Commenting is closed for this article.