2 ms·
The choice of tech stack for a desktop application seems like an interesting basis to claim a company has lost touch with its core values.
by YPPH 4y ago
The choice of tech stack for a desktop application seems like an interesting basis to claim a company has lost touch with its core values.
- smilespray 4y agoMoving from a native app to an Electron-based one has a definitive impact on usability. Calling it a tech stack choice is a bit dismissive. They used to have a kick-ass Mac app. That appealed to a considerable amount of their users. Then they ditched the native app for Electron, and those same users were disappointed.
- dcow 4y agoWhich functionality was removed by switch stacks? What is the actual usability impact? I currently use 1Password7 and haven't updated to 8 so I'd like to know before updating.
- skoskie 4y agoI’m fully in the camp who believes critical, top-level security should not co-exist with npm pulling dozens of 3rd party libraries which each pull even more 4th party code. Is there anyone here with a counter argument? Has a security review been performed on each dependency? Any reason to think my fear is unfounded?
- dcow 4y agoAnd what should replace it? Rust? Cargo? Oops. (I believe 1Password uses Rust for security-sensitive parts too, btw.) I'd genuinely like to know what the correct tech stack for a password manager is today because using the right one is important to my current endeavor. Regardless at Uno we're working on a password manager with a native app and rust core. It's geared more towards everyday consumers than power HN users, but you might find it interesting. The rust core including api server is open source right now because that's one point where we diverge from 1P. Whatever tech stack you choose, it needs to be openly auditable so that the community can collectively ensure it remains secure. https://github.com/withuno/identity https://github.com/withuno/identity