31–40 of 118 posts
Software is hard. Chrome had this in 2008. Firefox had to be rearchitected 14 years for this.
Browsers are too big and the web is too complex. Engineering failures all around. As engineers, we should not accept this status quo; we should replace it. We need a new web and new software.
Could anyone here who has been using it report their experience with site isolation turned on? Do you find anything it breaks or makes more difficult? Has it altered your privacy/security practices (in terms of addons, other settings, etc.)?
Has anyone tried this along with Container Tabs? Do they play nicely? Does it offer any advantage over Container Tabs?
Any idea? I'd love to drop https://addons.mozilla.org/en-US/firefox/addon/temporary-con... , which automatically assigns a temporary container to any new tab, which plays nicely with the https://addons.mozilla.org/en-US/firefox/addon/multi-account... but uses too much memory (at least from my experience).
Has anyone tried this along with Container Tabs? Do they play nicely? Does it offer any advantage over Container Tabs?
Any idea? I'd love to drop https://addons.mozilla.org/en-US/firefox/addon/temporary-con... , which automatically assigns a temporary container to any new tab, which plays nicely with the https://addons.mozilla.org/en-US/firefox/addon/multi-account... but uses too much memory (at least from my experience).
Using temporary containers, multi-account containers, site isolation, along with a number of other privacy/security addons such as Umatrix, LocalCDN, and many others, I have not noticed any slowdown.
This on an older broadwell i7 with 32GB of ram.
When Chrome was new and shiny, I used it for a time. Then, the first time I found myself needing to kill Chrome because it was completely locked up, I found myself staring at a wall of chrome processes in the task list, not knowing which one I needed to kill. At the time, I thought the idea of a separate process for each tab was silly. Though, with Firefox moving towards this model, I guess the engineers at Google we…
When Chrome was new and shiny, I used it for a time. Then, the first time I found myself needing to kill Chrome because it was completely locked up, I found myself staring at a wall of chrome processes in the task list, not knowing which one I needed to kill. At the time, I thought the idea of a separate process for each tab was silly. Though, with Firefox moving towards this model, I guess the engineers at Google we…
[1] https://hacks.mozilla.org/2021/05/introducing-firefox-new-si...
Earlier quoted context omitted.
Any idea? I'd love to drop https://addons.mozilla.org/en-US/firefox/addon/temporary-con... , which automatically assigns a temporary container to any new tab, which plays nicely with the https://addons.mozilla.org/en-US/firefox/addon/multi-account... but uses too much memory (at least from my experience).
I think they are complementary, since one is about browser site isolation, and one is about process isolation on the computer. Using temporary containers, multi-account containers, site isolation, along with a number of other privacy/security addons such as Umatrix, LocalCDN, and many others, I have not noticed any slowdown. This on an older broadwell i7 with 32GB of ram.
Earlier quoted context omitted.
hi, co-author of the blog post here. There is a more detailed blog post explaining how Site Isolation is better than the Electrolysis architecture here - https://hacks.mozilla.org/2021/05/introducing-firefox-new-si... (also linked to from the security blog post). Hope this is helpful!
Thanks for this link. Not sure how I missed it when it's the very last word, haha. I'm not sure what gave me the impression but, in my mind "process-per-tab" and "Electrolysis" were linked, but that was a misconception: >In great detail, (as of April 2021) Firefox’s parent process launches a fixed number of processes: eight web content processes, up to two additional semi-privileged web content processes, and four ut…
This always was a long term goal I think. It's per site not per tab though.
Software is hard. Chrome had this in 2008. Firefox had to be rearchitected 14 years for this.
This is factually untrue. Site isolation wasn't enabled by default in Chromium until v67 in 2018. https://www.chromium.org/Home/chromium-security/site-isolati...
http://www.scottmccloud.com/googlechrome/
In early-mid 2008, I created a comic book for Google explaining the inner workings of their new open source browser Google Chrome.
If I'm mixing this up with https://wiki.mozilla.org/Electrolysis, that's still 10 years.