"Rules" often contradict each other. For example, in software development, "keep it simple" often directly conflicts with "dont repeat yourself" as it takes increased complexity to achieve reuse of code. I often see keeping it simple take a back seat in newer developers as they slavishly follow the don't repeat yourself trail. The end result is routinely a brittle, rigid, and overly complex solution.
> but a properly security-paranoid home automation aficionado wouldn't be caught dead giving some proprietary black box power and network inside their own home.
Sure, if data from US would be enough to understand and fight disease. Otherwise, you need to create some sort of world health organization to share meaningful data and investigate inside all country participant without the appearance of [or actual] invasion of sovereignty.
Thus, we have the WHO. You wanna replace it, it's gonna take a decade to get to another agreement if one even is made. Then it will have its own set of issues. During a pandemic, seems better to me to work with and hold accountable the one we have... kinda like the WH is doing today.
Something along the lines barring the compilation of iOS apps with 3rd party tools or some such in TOS or blocking apps made with them from the App Store outright. Not saying the would, but if they had reason to fear they are losing control of something in their ecosystem, no telling what they would do. Just would not give a zero chance of something crazy as such happening.
Also "Frictionless sharing and collaboration" seems not valid at all when it exists in the closed ecosystem that is Apple. Probably the decision is to follow with Android and web [windows+linux].
Software development technology is getting close. A couple few more years maybe and that problem will start to go away fairly rapidly [relatively speaking], like possible 30-40% cross platform by the end of maybe 5 years-ish. 12 year android dev here seeing the light at the end of the tunnel with some newer performant (dev wise and user wise) frameworks and architectural patterns. Of course this all depends on Apple not saying FU to the entire industry in a dramatic, squashing those frameworks with their iron fist sorta way.
Signal seems a bit of a jerk company. They should have "stayed above the fray". Instead, they ridiculed. They were in their rights to do so but should have been the better. Throwing insults, however well grounded, is never good for a brand and shows a lack of level-headedness. They could have simple stated the story is a non-story and stated why. This could have been paired with working with the BBC to get a retraction in place, taught someone at BBC something, and maybe even gotten a little free positive PR from them in the process.
> Integrating a password manager with a browser is too fragile and risky way of using both. It is best to have them fully separated so they can't communicate. They should communicate exclusively via the user.
Which gets targeted more and why, the user or the password manager?
If you are suggesting that we should be manually entering passwords into sites as copied/observed from our password managers, that removes the anti-phishing benefits of password managers altogether by giving primary control back to the human. If I never type a password again, those hackers sending fake login page links "from my boss" will never gain me. Not so with no direct connection between my password manager and my browser.
A 2nd password manager for the 2nd part of the password breaks maybe the key advantage of this mechanism by putting the "something you know" into a decryptable by design storage space that is most likely duplicated in the cloud.
I switched my wife to FF from chrome and completely uninstalle chrome. She hates the inconvenience of any minor glitches or peculiarities - I hear a lot about it when she doesn't like something. I almost forgot she was switched over b.c. I didn't hear a thing about it from her.