Followup: modularity, WebExtensions, and going faster

[David Teller]

Of course, I should add

8. modularization should not kill startup performance, runtime
performance, binary size or memory usage.

On 11/10/16 10:29, David Teller wrote:
[...]
> So, here is my list of requirements for any proposal for modularity,
> assuming a Go Faster world:
> 
> 1. we need to be able to implement the APIs in at least JS and Rust;
> 
> 2. we need to be able to access the APIs in at least JS;
> 
> 3. we need to plan for the fact that many APIs will eventually be
> implemented out-of-thread or out-of-process;
> 
> 4. clear (and enforced) difference between private-to-feature,
> private-to-test, private-to-feature-set, private-to-firefox,
> private-to-system-addons and public-to-all-addons;
> 
> 5. typed APIs with rich types (e.g. not just "Object"/"nsISupports"), à
> la WebIDL;
> 
> 6. no hidden APIs;
> 
> 7. a clear place for the users of these APIs (including add-on authors,
> if they can access these APIs) to request new APIs, more documentation, etc.
> 
>