The GP is right on this one. Technical and other professional workers are generally to be left to their own devices. Micromanagement is only to be used on those with little experience and job knowledge, or specific cases of a problem employee. This has been thoroughly studied and well-known in the (educated) business community for decades.
Sexual orientation: pedophile.
Wow, you seriously just went for that, didn't you? Take it a step further. Don't hire men, because they're all alcoholics and rapists.
Wow 50 million PS3s? Increase that by another 50% and it's getting close to the number of Blackberry subscribers...
Which is, what, about 1.5% of cell phones?
If the software was never publicly published, it wasn't really open source software to begin with. You release early and you release often, also for these sort of things.
He released it to himself. I wonder if that is enough? If so, there are some strange implications for anyone coding for a living. Want to have rights to continue using your code? Add an open source license to it, even if the employer removes it later. Somehow, I think that there may be a reason this won't work.
The poster probably saw the chart, as they seem to have actually read the article in addition to merely glancing at a picture on the last page. Right below that graph:
But under the best of conditions, hard drives typically top out at 3% by the fifth year. Suffice it to say, the researchers at CMRR are adamant that today's SSDs aren't an order of magnitude more reliable than hard drives.
So you're quoting that SSDs are not 10x more reliable than HDDs. That doesn't exactly prove a point that HDDs are more reliable.
Lately we've also been finding out that many major websites are storing passwords as plain text and are untested against SQL injection. So it's unsurprising that they're also unpatched.
Web servers need to be actively watched, maintained and scanned for vulnerabilities. Just because it's a LAMP server doesn't mean it's rock-solid. The fire-and-forget philosophy does not apply.
The problem is generally far beyond the necessary LAMP or IIS patching: The vulnerabilities you describe are flaws in the site's design and code. You can't patch a stupid divaloper.
The problem is when you get beyond implementation, and the vendor has your data by the naughty bits. You can't just "walk" without walking away from all your data. You think you have an SLA that allows you to walk away with your data? Take a look and see if it defines EXACTLY which format they export it in. Chances are, you've agreed to get a few TB of incomprehensible junk if you break contract.
Regardless of the law, the choice is still between a) do what you're told and b) hope you can make your mortgage without a job.
The more I read your contributions to this story, the more it's becoming apparent that you're either a troll or a shill.