Changes

We're just getting started with WebExtensions, and have begun with a set of APIs that are commonly used with Chrome so people can kick the tires. We don't want to be a Chrome copy, and we want to ensure we differentiate while integrating Electrolysis and other initatives into Firefox. To innovate will require input and assistance from the community, which we are actively seeking. The path for WebExtensions will evolve in the coming weeks, months, and years, and we want the developer community to be a big part of that evolution. === Why are these big changes needed? === We believe that moving Firefox away from XUL and XPCOM is a long-term strategic necessity. We need These technologies are 15 years old and no other browser uses them. It doesn't make sense for us to continue to invest in them, but at the same time our performance and security depends on them. However, we can't even begin to find a way move Firefox off of these technologies until we know how to do thatevolve add-ons as well. We have announced WebExtensions and the deprecation as early as possible so that we can get feedback from the community on how to make the transition. We know that WebExtensions will need to be improved. To innovate We also know that XUL will require input and assistance from the community, which we are actively seeking. The path continue to live in some form for WebExtensions will evolve in the coming weeks, months, and years, and we want the developer community to be a big part of that evolutionwhile.