zlacker

>>akyuu+(OP)
There was a time when Firefox felt a lot slower than Chromium, but for a few years now it's been close enough (even if still somewhat slower) to not bother me, while Firefox clearly offers superior functionality and much better performance under high load. The last time Chromium has felt attractive compared to Firefox was a really long time ago. Glad to see it moving in the right direction still.

>>seba_d+35
I switched to Firefox from Chrome years ago because Chrome was slower. Specially, when there were many tabs opened, switching tabs in Chrome were usually prefaced with a blank white screen for about 2 seconds.

I've been staying with Firefox not for the performance (today Chrome loads Google sites like YouTube faster), but mainly for Tree Style Tab extension. I couldn't imagine opening more than a dozen of tabs without it.

>>beltsa+Lz
I've stayed (edit: with Firefox) because of (1) containers and (2) password storage. I have to use Chrome for some things, and every now and then it prompts me for a password and refuses to use the auto-fill. Totally torques me off because my passwords are not easy.

But I completely trust Firefox on the password issue, to the point that I let it generate them for me.

>>dhimes+Qx1
>But I completely trust Firefox on the password issue, to the point that I let it generate them for me.

Not that I don't trust them but I always recommend using a dedicated PW manager like KeePassXC which is FOSS and has been security audited, plus it gives you full control over where you get to store your PWs and how they're secured and generated.

>>Firmwa+Bz1
To be fair, Firefox is also FOSS, contains an integrated password manager with extraordinarily well-integrated browser compatibility, and by opting to use a master password to encrypt or decrypt the store also gives you control over securitization, storage location, and generation.

Not to say that KeePassXC isn’t useful if you want even more fine-grained controls, but it seems like in the

> Use password in browser

Use case, KeePass would actually weaken the security guarantee by adding a second component you need to trust.

>>fardo+QI1
> adding a second component you need to trust

I'd even say "adding a second vendor you need to trust". Yes, these days there seems to be a strong drive to just get a big package out of a single hand. Like having the browser closely tied to the OS. I don't like it. I prefer to choose the individual parts as i see fit. Keepass and some bit of custom sync, in this case. Now, in the same vein I expect MS & Google making it easy to support different browsers, I'd want Mozilla making it easy to integrate other password managers. I'd love to be corrected, but afaik the "password manager with extraordinarily well-integrated browser compatibility" doesn't offer any way or API to connect my keepass with it. Its only for Mozilla's own stuff. Not the open, user controlled system i'd love Firefox to be.

The Firefox Android Addon system is even worse... only a very short list of pre-approved extensions are available. With the escape hatch for devs requiring some stupid online-account. Sorry, but how is that different from an App store without side-loading?

Still recommend using Firefox, since it is the best we have. But yeah, i don't like the less and less open direction apparently chosen by Mozilla. And wonder if not being a good role model will hurt them down the line...

>>Faark+Ai2
>The Firefox Android Addon system is even worse... only a very short list of pre-approved extensions are available.

You need to install Firefox Nightly.