[cedws]

How did you come to the conclusion that this very recent issue is 1Password’s fault and not Electron’s?

[oarsinsync]

1Password used to ship native (aka "Mac-assed") apps. They (relatively, in the software's history) recently switched to Electron instead of continuing native app development.

[crazygringo]

So again, how does an Electron bug become 1Password's fault?

It's cross-platform and integrates with browsers so it makes sense they would want to use a cross-platform JavaScript solution as much as possible. Not just to make their developers more efficient, but to reduce the surface area for bugs and vulnerabilities.

[macintux]

1Password used to be an excellent native app. It's not surprising that many users (myself included) resent the enshittification.

[crazygringo]

I've used it for years and am only finding out today that it's Electron. And I couldn't care less.

99.9% of my usage is within the browser plugin anyways. And whenever I have to edit an entry, it works fine.

[aniviacat]

> 99.9% of my usage is within the browser plugin anyways.

If you don't (or barely) use the app, the app is not an issue to you; that seems pretty self-evident.

The experience for regular users may differ.

[crazygringo]

What is the problem with it? And isn't everyone using the browser plugin anyways mostly? Isn't that where the vast majority of passwords get entered?

[zen928]

You personally disliking something isnt enshittification.

[macintux]

It was done at roughly the same time that the company switched to a subscription model and their focus switched from consumer to business.

[jen729w]

...shortly thereafter, Apple released their own Passwords app, largely Sherlocking 1Password from a consumer perspective.

If this had been your business, what would you have done? I would have done exactly what they did.