Seeing that today is a slow news today we’ve decided to dig around the web and see what kind of glittery magic you can find there. As it turns out, Mozilla has recently did the IAMA session on reddit, which can be found on the following page.
Interestingly enough, the open source organization has revealed that they are re-evaluating Electrolysis (e10s), the multi-process architecture that they canned back in 2011. What was the point of it (other than process isolation)? Offer better UI responsiveness, stability and performance on multi-core machines.
Q: Chrome does a lot with privilege separation and process isolation to create a bit of a fail-safe setup. How can Firefox’s monolithic process model compete from a security standpoint? Have any/are any steps being taken to isolate components more (other than plugins)? What’s happening with e10s?
A: There is a new effort underway to evaluate e10s, again. The biggest issue was that addons, which make Firefox so useful and extensible, at the same time were mostly incompatible with process separation. One way to solve that is to have “Proxies” and “Wrappers” that pass different operations between the processes. This is however not a very clean solution, so the new Addon SDK (“Jetpack”) was built with sandboxing in mind.
You can learn more about Electrolysis here.
About (Author Profile)
Vygantas is a former web designer whose projects are used by companies such as AMD, NVIDIA and departed Westood Studios. Being passionate about software, Vygantas began his journalism career back in 2007 when he founded FavBrowser.com. Having said that, he is also an adrenaline junkie who enjoys good books, fitness activities and Forex trading.