If anything I’m MORE willing to pay a subscription for a password manager. I expect and want it to continue to be developed and for the services to be rock solid and secure.
That's the theory, but unfortunately I haven't really been seeing 1Password deliver on that promise. Updates don't seem to be all that frequent / significant, and yet several pretty serious issues remain in the app years after reporting them.
The most egregious flaw is that if you have multiple passwords for the different accounts hosted on different subdomains (e.g. service1.example.com vs. service2.example.com), 1Password doesn't correctly differentiate. If you visit service1.example.com, autofill your credentials there, and then visit service2.example.com afterwards, 1Password will try to autofill the credentials from service1 on service2. (Whichever one you autofill first gets priority, though this resets after some amount of time.)
It's certainly a little unusual to have completely different services hosted on different subdomains, but there's absolutely no reason the website at service1.example.com has to have
anything to do with service2.example.com. This is really no different than autofilling a password from, say, apple.com on google.com. (And yes, I do have all the password entries correctly configured with the correct websites. This bug was introduced with an update ~3 years ago.)
Other than this, 1Password autofill support is frequently flaky and/or just broken in one way or another. The number of times I've had to kill every process related to 1Password and/or restart my browser (depending on what's wrong, one, the other, or both may be required) just to get autofill working is ridiculous.
There's also the time 1Password prepended "http://" to all my website fields on an upgrade (I don't put full URLs in that field, because they always change eventually), causing 1Password to start warning me that every single website was insecure. But at least that was a one-off I've been able to fix one password at a time as I hit the warning.