I've been using Linux on my desktop since running AfterStep WM on RedHat in 1996. My current machine is running Mint Cinnamon 17...
Both of our Android phones both have multi-user capability.
That may be a true statistic, but the subset of 51% of people who are stupid are not necessarily the same as the subset of 51% that share their passwords.
There are two people who have access to all of my passwords: My wife and my lawyer.
These are the only two people on this planet with whom my communications are protected by legal privilege.
Should the thinkable happen (let's face it, calling untimely death unthinkable is stupid, as it is entirely thinkable), there should be someone left who can access everything to put my affairs in order.
Gee, you don't say?
Because I'm not. But, where does the 92 billion light year thing come from? I would think what, 28 billion across if it's 14 billion years old?
People who aren't USAsians who know that MM means 1000 * 1000 which is French for 1,000,000
If I put a supercap made of organic hemp into an oven at 105C for 5000 hours, what's left when I am finished? It is still a supercapacitor or is it a small metal can full of organic goo?
What is this "female body" of which you speak?
You missed my point entirely. I'm not saying people don't make mistakes. I'm saying I want the guy who does validation work and debugs his shit BEFORE handing it over to the customer, not AFTER.
Let me put it this way. When I hire an engineer, do I want to hire the guy who gets stuff right the first time, and thoroughly validates and identifies and fixes little issues before publishing results? Or, do I want to hire the guy that gets it done, hurries to publish results with tons of niggling little problems, and ultimately gets it right after several iterations of fixing minor problems?
Of course I want the first guy. Yes, lots of development has issues, but if the government is finding all of these little issues that can be fixed "within hours," you'd think SpaceX would have a good enough process in place to find and fix those trivial errors before releasing results or product.