You missed the part about Chrome OS and everything becoming a web application, not a static web site. If all modern web browsers can run javascript like native code, it will change the way programs are distributed, and in fact, will lead to a safer computing environment, since you won't have to install any of it locally. In the meantime, look into noscript if you're that concerned, and look forward to better web applications that run like native applications.
While the code name is electrolysis, it is called Content Processes. According to this https://wiki.mozilla.org/Content_Processes#Phase_II:_Parallel_Improvements , the project is still lagged behind on completing Phase 2, projected to be completed November 1st, 2009. The real multiprocess work isn't even going to hit until Phase 4, which is going to be months from now. I'm really not sure what the author of that blog tested, since the only multiprocess aspects of the electrolysis build are disabled by default, requiring dom.ipc.plugins.enabled to be set to true in about:config. It is not necessary to compile the build yourself either, as the latest electrolysis nightly build can be found here: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-electrolysis/ precompiled for your enjoyment, not that it matters.. since it's so early in the development process that there is no benefit whatsoever outside of helping them track bugs.
Slashdot Mirror
You missed the part about Chrome OS and everything becoming a web application, not a static web site. If all modern web browsers can run javascript like native code, it will change the way programs are distributed, and in fact, will lead to a safer computing environment, since you won't have to install any of it locally. In the meantime, look into noscript if you're that concerned, and look forward to better web applications that run like native applications.
While the code name is electrolysis, it is called Content Processes. According to this https://wiki.mozilla.org/Content_Processes#Phase_II:_Parallel_Improvements , the project is still lagged behind on completing Phase 2, projected to be completed November 1st, 2009. The real multiprocess work isn't even going to hit until Phase 4, which is going to be months from now. I'm really not sure what the author of that blog tested, since the only multiprocess aspects of the electrolysis build are disabled by default, requiring dom.ipc.plugins.enabled to be set to true in about:config. It is not necessary to compile the build yourself either, as the latest electrolysis nightly build can be found here: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-electrolysis/ precompiled for your enjoyment, not that it matters.. since it's so early in the development process that there is no benefit whatsoever outside of helping them track bugs.
You need to read this. http://skeptoid.com/episodes/4058#