1Password for Mac Moving to Electron
91–100 of 201 posts
Re: 1Password for Mac Moving to Electron
#921Password and the Tower git client were somewhat similar: They started on native Mac first and years later introduced a native Windows version that lacked behind in features and polish. 1Password for Windows slowly(!) caught up, and even after all this investment, they decided that going for a web-based UI across all desktop OSes is the better solution. Tower did not change this: Their Windows version is still lackin…
Re: 1Password for Mac Moving to Electron
#93Earlier quoted context omitted.
I kind of don't understand why customer support would answer customer questions that way — Oh my, did you just a question about Electron? Because I swear you asked about our RUST BACKEND. Let's talk more about that.
> I kind of don't understand why customer support would answer customer questions that way — Oh my, did you just a question about Electron? Because I swear you asked about our RUST BACKEND. Let's talk more about that. I see two possibilities: 1. They were told "it was written in Rust, mention that a bunch and link this blogpost for street cred" and actually have no idea what either Rust or Electron is beyond they're…
Re: 1Password for Mac Moving to Electron
#941Password and the Tower git client were somewhat similar: They started on native Mac first and years later introduced a native Windows version that lacked behind in features and polish. 1Password for Windows slowly(!) caught up, and even after all this investment, they decided that going for a web-based UI across all desktop OSes is the better solution. Tower did not change this: Their Windows version is still lackin…
I think the whole idea behind Electron is that they've also put out a native Linux version. Which is much, much better than having to run an extension in the browser, and gets some system integration (unlock with yubikey).
From the screenshots, it would seem the Mac version is the same as the Linux version (currently version 8.1.1 on my machine). One big step back is if you have multiple vaults (say personal + company) you have to open each one individually. No more one password unlocks everything.
Re: 1Password for Mac Moving to Electron
#95Re: 1Password for Mac Moving to Electron
#96Earlier quoted context omitted.
Why do you think it’s going to be slower, and in comparison to what?
> Why do you think it’s going to be slower Have you ever used an electron app? Typically slow and laggy. Worse, your workflow is typically slower since the user don’t get any the advantages of native integration.
They didn't even bother using a real window for the app settings, they just use an Electron modal window.
Re: 1Password for Mac Moving to Electron
#97Could someone give a bird's eye view summary of why 1Password moving to Electron is bad? Are there documented security risks, or is it more just a UX/UI aesthetic issue?
It's popular to hate on Electron. The most common argument thrown around is "bloat". I also detect a perception among engineers that they consider Electron "the easy way out" vs. maintaining strictly native apps. Reminds me of the discourse around Sharkbite fittings on plumbing forums. I have to wonder what percentage of 1Password users know what languages or frameworks 1Password uses, much less care what languages o…
Re: 1Password for Mac Moving to Electron
#98Earlier quoted context omitted.
In addition to the bait and switch comment, 1Password is an always-running app. Congrats, they just decided 1500MB of your ram is theirs now.
I'm using the Windows beta, and there are 3 background process. One is using 4.5mb of RAM, one 32, and one 43.9.
Re: 1Password for Mac Moving to Electron
#99What was even the value proposition of using 1password over the native keychain access on mac? Generating passwords? Safari does this now (albeit always ignores the website's specific password rules and gets it wrong most of the time)
Re: 1Password for Mac Moving to Electron
#100Could someone give a bird's eye view summary of why 1Password moving to Electron is bad? Are there documented security risks, or is it more just a UX/UI aesthetic issue?