There's a big movement in the Web community to move everything to JavaScript. Js on the server side with Node, html generated by Javascript, and the latest trend CSS-in-js.
On one hand, this can be argued as centralizing on one technology that will reduce long term cost because the operational stack around it can be reused: tests, build tools, deployment. However it very much can be seen as adding another technology to manage since it's adding a shiny new library to maintain with all the bugs and kinks along the way.
The things that held me back from Bitwarden is the relatively short age of the company at 2~ years and the fact that there is only one dev. I'm reaching here. But even though the code is open source, he still owns the distribution. He can potentially be compromised (whether maliciously or not) and release an update that uploads the entire vault to him unencrypted. It could take a while before the internet caught on that the source code doesn't match the release build.
This of course could happen in a company like 1Password and there is at some point that I need to make the call and trust the person(s) coding the password manager. I feel that with 1Password there's at least the large size of the company which would mean more eyeballs and accountability. There is also the history of the company at 12~ years. This includes vetting and buy in from larger companies, which inspires a vote of confidence.
FWIW Bitwarden checks off nearly all the other boxes for me and I think the single dev has done a seriously bang up job.
> - They still run in a browser. It shows an address bar and whatever else your browser is always showing. Try Twitter's PWA right now: https://lite.twitter.com It's way too easy to accidentally swipe back. And then, Twitter being a shitty Single-Page-App, the browser loses its scroll position.
Android doesn't show the address bar. I don't have iOS but it seems like Safari support for PWA isn't as far along as Chrome.
I see WebExtensions as taking a good/easy API that the Chromium team has created and proven and standardizing it like they standardized the web.
I never worked on the previous Firefox extension API but I find it ridiculously easy to have a cross platform extension that works on Chromium and Firefox. That counts for something.
This decision makes sense. I'm assuming that they're going with the platform native notification APIs now.
With the release of Windows 10, all three platforms (Windows, Mac, and Linux) now have a native notification center that supports persistent notifications that were missed or haven't been dismissed.
The Chrome's notification center was always out of place for Linux and Mac users since there was already a fully featured native notification center that wasn't being used.
On one hand, this can be argued as centralizing on one technology that will reduce long term cost because the operational stack around it can be reused: tests, build tools, deployment. However it very much can be seen as adding another technology to manage since it's adding a shiny new library to maintain with all the bugs and kinks along the way.