I tried really hard to make FF my main browser. I really did. But I was disappointed by their "hybrid" approach to memory use, and I think that continues to make the difference between FF and Chromium-based browsers (to FF's detriment).
And now they switched back to shared memory again, and the moment they did, the browser started hanging again, like it used to do pre-Quantum days.
Chromium's "per process memory isolation" is the right approach, despite all the cries about memory use. I'd rather have that than have the browser hang on me, or have more security issues.
If anything, I think even the future of operating systems is complete process isolation and separation by virtualization tech and encrypting each process in RAM with a different key. The hardware is coming, but it may take another 10-15 years for this to be fully realized.
And now they switched back to shared memory again, and the moment they did, the browser started hanging again, like it used to do pre-Quantum days.
Chromium's "per process memory isolation" is the right approach, despite all the cries about memory use. I'd rather have that than have the browser hang on me, or have more security issues.
If anything, I think even the future of operating systems is complete process isolation and separation by virtualization tech and encrypting each process in RAM with a different key. The hardware is coming, but it may take another 10-15 years for this to be fully realized.