5 ms·

I tried 8 on Windows. I went back to 7 after a week. * Search is just plain broken. This was the number one reason i scrapped it. * Managing multiple vaults (

I tried 8 on Windows. I went back to 7 after a week. * Search is just plain broken. This was the number one reason i scrapped it. * Managing multiple vaults (i have over a dozen) is unusable. * The UI is terrible, it takes way more space to show less information than 7. * The browser integration (FF) seemed to work poorly. Basically, once 1Password stops supporting 7, they will have lost me and anyone I can influence as a customer.

vladvasiliu 5y ago
While I fully agree with your issues, and have experienced them too, (although comparing v8 on Linux to v7 on Mac – I don't use 1Password on Windows), those are just UI/integration issues. I don't think they're because of electron, but rather because the remake of the UI is poor. FWIW, my main gripe is having to unlock each vault separately, as opposed to a single unlock as used to be the case on Mac / iPhone.
- toyg 5y ago
  > those are just UI/integration issues. I don't think they're because of electron Electron makes integration harder.
  - vladvasiliu 5y ago
    Fair enough, but I expect browser integration and so forth to be done via the backend, which is rust, so native.
    - toyg 5y ago
      Rust is hardly a "desktop-native" language. I expect it will have to jump through all sorts of hoops to interface with the Obj-C underpinnings of MacOS desktop libraries. Regardless, even if the backend were pure Obj-C, the point is still that now you have a UI stack and a backend stack, instead of a single desktop-native stack, and you have to manage their communications. But I guess the money they save by not managing desktop-specific codebases eventually adds up...
  - lillecarl 5y ago
    Why? You don't have to use Electron for everything, you can integrate using whatever language you want and some RPC, like Keybase did.
    - toyg 5y ago
      And that's still more involved (and slower) than "just use this function that desktop vendors helpfully provided for the purpose".
      - lillecarl 5y ago
        That one part yes, but if you can build most of your application cross-platform and only do certain things with "native" solutions you might get better bang for the buck. Discord and VS Code comes to mind.

vladvasiliu 5y ago

While I fully agree with your issues, and have experienced them too, (although comparing v8 on Linux to v7 on Mac – I don't use 1Password on Windows), those are just UI/integration issues. I don't think they're because of electron, but rather because the remake of the UI is poor. FWIW, my main gripe is having to unlock each vault separately, as opposed to a single unlock as used to be the case on Mac / iPhone.

toyg 5y ago
> those are just UI/integration issues. I don't think they're because of electron Electron makes integration harder.
- vladvasiliu 5y ago
  Fair enough, but I expect browser integration and so forth to be done via the backend, which is rust, so native.
  - toyg 5y ago
    Rust is hardly a "desktop-native" language. I expect it will have to jump through all sorts of hoops to interface with the Obj-C underpinnings of MacOS desktop libraries. Regardless, even if the backend were pure Obj-C, the point is still that now you have a UI stack and a backend stack, instead of a single desktop-native stack, and you have to manage their communications. But I guess the money they save by not managing desktop-specific codebases eventually adds up...
- lillecarl 5y ago
  Why? You don't have to use Electron for everything, you can integrate using whatever language you want and some RPC, like Keybase did.
  - toyg 5y ago
    And that's still more involved (and slower) than "just use this function that desktop vendors helpfully provided for the purpose".
    - lillecarl 5y ago
      That one part yes, but if you can build most of your application cross-platform and only do certain things with "native" solutions you might get better bang for the buck. Discord and VS Code comes to mind.