pinpelipon

That is a very good article! I bookmarked it in 2013 for that reason. :)

The thing just is... A CEO doesn't really care whether there are 1500 or 1502 workers. Some idiot drops one engine on the assembly floor breaking it. Accurate statistics is an oxymoron. The bitcoin transfers are reliable (mathematically proven even), but does it matter if your wallet shows a wrong number in the UI for a while? I had a good friend go to ATM on a Friday night and see that his current balance was 2.4 billion euros. Next morning it was corrected, and nothing really bad happened.

For the business it is more important to find the (very rare) screw-ups and correct them. You don't really have to do it in real-time either. A 1960s style batch job is just fine.

The reason for previous is that the full ACID model system will fail with the same starting values. The difference is that it tells that end user something like "uh-oh, something went wrong and we can't process your transfer or whatever" (common with banking applications) when eventually consistent model allows the process to continue, and the screw-up must be handled at later stage. From the end user's point of view the ACID version is usually much worse.

I work for govt, and I'd like to buy a lot of open source support contracts. As long as they are under the purchase limits that would force full tendering process things should be easy. But I simply can't donate.

There are two reasons several of my clients have chosen Oracle over Postgres.

#1: Training. Oracle does training very well. If need new DBAs in-house (for security reasons etc), they got huge array of options available. The most effective options are also insanely expensive. Once paid 400k€ to get two new DBAs. They became very good at it.

#2: Clustering. Postgres is nowhere near what Oracle offers. Even with the newest releases. What Oracle offers is real multi-master synchronized replication with proper distributed locks, low latency, and it's maintainable and easy to setup. Postgres has still 5-10 years to do before they will reach feature parity on today's Oracle.

To be fair, most of the developers raving about ACID I have met have had trouble naming other valid use cases requiring full ACID besides the "transferring money from an account to other" that nearly every course and school uses. The thing is, most of the applications just don't need that kind of guarantees, if they can at least detect (when using BASE) when something went wrong.

Tritium & tritiated water can be somewhat easily separated from water. Just freeze the mixture, and it forms layers. However, there probably is quite a bit of tritiated water.

Also, SELinux is not about just files. It controls some capabilities, and can be used to control the data inside applications as well.

Ditto! We are approaching temperatures that could actually support the hardiest of palms. We can start replacing the spruces with palms soon.

The downsides being ticks becoming common, warmer temperatures enabling more diseases spreading in both human and animal populations, a few native animals dying (they can't breed without certain things such as ice, and their natural defense mechanisms do not work), and Gulf stream probably slowing and causing a new ice age. Ah yes, there's always that. But then again, not going to happen on my lifetime so who cares... :)

Does this mean that some day I might be able to buy a cell phone that has a radio chip that is not full of buffer overflows and other types of flaws?

Combining both the ancestral and the ACL system was botched.

Both are good on their own. The hybrid model is complex and hard to manage, even though it can technically fulfill most requirements you can think of.

It's a real shame because it means ACL usage is not going to take off anywhere soon.