3 ms·
For me Firefox is just superior to Chrome with the Tree Tab Style extension and the absence of multi-process. The multi process in Chrome is implemented in a v
by hokkos 12y ago
For me Firefox is just superior to Chrome with the Tree Tab Style extension and the absence of multi-process.
The multi process in Chrome is implemented in a very bad way that multiply without a reason the RAM usage, it is better implemented in Safari but still heavy, I eventually have crash in Firefox once a month, but the session manager addon can remedy. As for addons they use way less memory in Firefox, you can see it with the about:addons-memory addon (yes another one), "add block edge" uses around 25MB, whereas in Chrome it is 10x more. I still use Chrome for webdev, but the firefox dev tools are progressing.
Tree Tab Style is a better way to navigate the web, you can see more tabs because screens are wide and the web is vertical, so it makes a better use of the screen. Also the tree structure is better for the way to browse the web with hyper-links, it is like a multi stack trace of page you saw.
- findjashua 12y agocould you please explain in layman terms what exactly is bad about the way multi-process is implemented?
- hokkos 12y agoIt is explained here : https://trac.webkit.org/wiki/WebKit2 https://trac.webkit.org/wiki/WebKit2 and here : http://webkit.sed.hu/blog/20110120/webkit2-memory-consumption-process-models-vol-1 http://webkit.sed.hu/blog/20110120/webkit2-memory-consumptio... Chrome duplicate tons of data structures, Webkit2 shares more, but Firefox without multi process is more efficient.