3 ms·
Firefox's killer feature was generating sync keys locally and letting you self-host a compatible sync host. Chrome generates the sync keys on server and has pr
by zelly 7y ago
Firefox's killer feature was generating sync keys locally and letting you self-host a compatible sync host.
Chrome generates the sync keys on server and has proprietary sync software.
That's it. That's all it took for me to switch. I know FF eats almost double the CPU compared to Chrome. I know 1 out of every 10 webapps will just not work in it. That's fine. I will take the security and privacy over convenience.
Just buy a better CPU.
- aequitas 7y ago> Just buy a better CPU. This gets a little hard when the device you want to run FF on is a old laptop that doesn't need replacing and where battery life is more important than raw speed.