Proposals for future Firefox browser architecture
Перейти к файлу
Emily Toop a30f0396b4 address review comments 2018-05-24 17:46:23 +01:00
_layouts Fix links to newsletters. 2017-09-25 13:08:54 -07:00
assets/css Add a basic Mozilla theme 2017-08-22 19:24:13 +01:00
experiments address review comments 2018-05-24 17:46:23 +01:00
newsletter/_posts Add newsletter 5 2017-11-29 13:03:04 -08:00
text fix typo nits 2018-04-11 16:59:54 -07:00
.gitignore Add github's config to allow running the site locally. 2017-09-25 17:45:51 +01:00
Gemfile Add github's config to allow running the site locally. 2017-09-25 17:45:51 +01:00
ISSUE_TEMPLATE.md Add issue template 2018-01-23 11:31:48 +00:00
LICENSE Initial commit 2017-07-19 15:40:10 +01:00
README.md rkv design review. 2018-04-11 11:19:50 -07:00
_config.yml Fix links to newsletters. 2017-09-25 13:08:54 -07:00
newsletters.xml Fix links to newsletters. 2017-09-25 13:08:54 -07:00

README.md

Firefox Browser Architecture

Vision

Build the worlds best web browser

Strategy

Our top priority is to plan for where we want to go, but if we just think 5 years out, well miss the dragon on the doorstep. So we need to look from both angles:

  1. Look forward from where we are now: Move faster
  2. Look backwards from where we want to get to: Consciously plan our architecture

Our Conclusions

This is a list of our findings that we're reasonably happy with so far.

Posts

We typically send our newsletters to firefox-dev.

Explorations and Experiments

To support our conclusions we occasionally perform explorations and experiments. The first exploration is designed to support the notion that we can create a sync and storage layer in Rust that we can deploy to Desktop, Android and iOS.