Proposals for future Firefox browser architecture
Перейти к файлу
Joe Walker fa0471337b Add a basic Mozilla theme 2017-08-22 19:24:13 +01:00
_layouts Add a basic Mozilla theme 2017-08-22 19:24:13 +01:00
assets/css Add a basic Mozilla theme 2017-08-22 19:24:13 +01:00
posts Add the text of our initial post to firefox-dev. (#3) r=rnewman 2017-07-27 11:13:59 -07:00
text Link recent posts and move files to the right places 2017-08-16 12:19:39 +01:00
.gitignore Initial setup containing vision and strategy 2017-07-19 16:07:05 +01:00
LICENSE Initial commit 2017-07-19 15:40:10 +01:00
README.md Link recent posts and move files to the right places 2017-08-16 12:19:39 +01:00
_config.yml Set theme jekyll-theme-minimal 2017-07-19 15:45:51 +01: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

  • Documenting our output looks at how were going to communicate with the rest of Mozilla.
  • Extracting Necko considers whether it's feasible or worthwhile to extract Necko — Gecko's C++ networking library — for use as a standalone component.
  • XUL problems aims to list the different kinds of problems that exist with XUL.
  • XBL and Web Components compares some old Mozilla technology (XBL) with modern Web Components.

Posts