canmove, Confirmed users
548
edits
Jetpack/Roadmap-2011: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 16: | Line 16: | ||
To that end, our top priorities for 2011/2012 are: | To that end, our top priorities for 2011/2012 are: | ||
1) ''Enable jetpack to always create add-ons that take advantage of the Electrolysis (e10s) to run in a separate process.'' Running an add-on in a separate process is important for users and the add-on developer as it makes it much easier to determine if an add-on is affecting the browser's performance. In addition, there may be some security enhancement as its much harder to exploit a vulnerability if its being run in a separate process. For Jetpack, we want to ensure that our users never even have to think about e10s or how to use it for their add-ons to run in a separate process. | 1) [[Features/Jetpack/Out-of-Process_Addons | ''Enable jetpack to always create add-ons that take advantage of the Electrolysis (e10s) to run in a separate process.'']] Running an add-on in a separate process is important for users and the add-on developer as it makes it much easier to determine if an add-on is affecting the browser's performance. In addition, there may be some security enhancement as its much harder to exploit a vulnerability if its being run in a separate process. For Jetpack, we want to ensure that our users never even have to think about e10s or how to use it for their add-ons to run in a separate process. | ||
2) ''Create a path for developers using the traditional tools to move to jetpack.'' If we are successful in bringing in new developers creating new add-ons we must not forget the developers who have been using the traditional toolset. With the inclusion of e10s and mobile, it becomes imperative that we offer the easiest methods possible to create add-ons that work with these new technologies and platforms. We see Jetpack as being a great path for these to start taking advantage of these new features - as long as we can make the porting equally simple. This work includes creating tools which will automatically help developers port their existing add-ons, as well as a good set of documentation and examples to help them understand the differences in approach. | 2) ''Create a path for developers using the traditional tools to move to jetpack.'' If we are successful in bringing in new developers creating new add-ons we must not forget the developers who have been using the traditional toolset. With the inclusion of e10s and mobile, it becomes imperative that we offer the easiest methods possible to create add-ons that work with these new technologies and platforms. We see Jetpack as being a great path for these to start taking advantage of these new features - as long as we can make the porting equally simple. This work includes creating tools which will automatically help developers port their existing add-ons, as well as a good set of documentation and examples to help them understand the differences in approach. | ||