沒提有沒有要引進量子引擎??
-------------------------------------------------------------------------------
Waterfox as it is is where I want it to be:

It is stable in terms of development time
There is good support for (most) classic add-ons
There is good support for (most) WebExtensions
Backporting WebExtension APIs is more straightforward to this version.
The performance gains from the newer developments in Firefox are apparent
A lot of the privacy hampering features have been outright removed or disabled where more complicated (and this is where a big focus will be on)
Future updates include security patches, removing more telemetry, reviving old requested features and back porting where possible
Classic extensions have all been archived, all that is left is to create a catalog for them.

Overall, this is a good experience for users because it is a consistent one. But, it isn’t possible to keep like this forever. The future variant will be:

Based on ESR releases
Ability to develop “classic” style add-ons. Mozilla does this internally, I think it’s worth exposing this to developers in general. There is good reason for Mozilla to want to do this, but we are aiming for a more technical crowd.
Add-on developers will be given plenty of time for the expected features in the next releases and ample time to update their add-ons (imagine a 1 year 6 month release cycle, notify 3 months before any API changes)
Independent add-on store (with potential for developers to earn money as well)
Latest HTML standards will be kept up to date in a timely enough manner without having to be on the forefront (adoption takes time regardless!)
Support a myriad of protocols (ideally supporting Tor as well) and media formats (and since we’re EU based, I really want to move away from binaries that are provided by Cisco for H.264 playback)
https://blog.waterfoxproject.org/wa...g-to-the-future