> Especially with 1Password's ability to generate 2 factor tokens and put them in your pasteboard automatically so you don't ever have to pull up an Authenticator app!
Bitwarden also does this.
I still felt its sluggish performance on launch/search/sync was slowing me down a lot throughout the day.
I recently switched (maybe 5 weeks or so, ago, from 1Password to Bitwarden, after finding out about it on HN) I imported ~400 odd logins from 1Password, I honestly don't find it any slower than 1 Password.
I did notice that with Discord, both 1Password and Bitwarden now integrate with the new iOS password apis.
IIRC from their Github issue threads, Bitwarden is using Xamarin, and performant UI has been a consistent struggle with many login entries.
Also, having combed through my entire catalog by having to manually import Bitwarden to 1Password, I’ve realized all those random startups I’ve made a login for or various sites for applications (job/school/etc) really add up quickly!
I have over 1500 entries in my password manager. That's the result of using it for years and having every single account I signed up for registered in it. Including random forums I only ever posted once for support. So yes, people can have more than 100 entries in their password manager.
I switch from LP to bitwarden because I didn't trust LP anymore. It's fine but I find the autofill very dumb (will usually overwrote your password or random fields in various forms), and doesn't do subdomain matching well. Search or just opening the extension (on Firefox) is sluggish, and the android app is very slow (open and search). Automatically putting the 2FA in the clipboard has never worked for me either (Firefox on Linux). But I'll keep using it anyway because it's FOSS and not LP. You can even self host your instance if you like.
Bitwarden's support via IRC/gitter was exceptional when I was experiencing issues with it. Not only did they fix the problem, but they provided a custom build for me with more verbose logging enabled and worked with me directly to figure out what the issue was. It was fixed in a couple of hours and I was able to run the patched build without issue until the fix had been merged and released.