The productivity gains from AI will make new jobs possible and will free up capital to be deployed in new economic creation. That is a cycle that has been essentially non-stop for the last 200-300 years (particularly aggressive and accelerating in that time frame). As populations decline and population growth stagnates, we won't have anywhere near enough people to fill the job openings in the future. The working class will benefit extraordinarily from the AI boom, it will raise their wages, it will produce an immense bounty of new jobs that will mostly go unfilled and it will drastically improve their standard of living.
Of course, was a joke. But there will always be more work that we can possibly do. You are never really done in a successful business. So I feel sad that he made these sacrifices at the expense of his family life. The saddest part is that the code he wrote will probably be a distant memory in 20-30 years.
What stops the person taking the payment from pushing the switch button accidentally or intentionally. Also I can totally see how people can steal your card, use the app to put it into their coin then place the card back so you don't know you've been robbed.
As far as we know, Datomic's (noninteractive) transactions are ACID. You would do better to ask them, though. The list isn't intended to be exhaustive!
From what I understand, Datomic sidesteps the ACID issue altogether by dealing with immutable data at the application layer. You add your changes on top of a version of the database, so you're always working on a consistent view of the database (pretty much like Git).
On the backend, Datomic doesn't implement it's own storage, it plugs into SQL databases, Riak, etc. so you may or may not have ACID at that level.
No, they lock the entire database for every write.
"MongoDB uses a readers-writer [1] lock that allows concurrent reads access to a database but gives exclusive access to a single write operation."
"Beginning with version 2.2, MongoDB implements locks on a per-database basis for most read and write operations. Some global operations, typically short lived operations involving multiple databases, still require a global “instance” wide lock. Before 2.2, there is only one “global” lock per mongod instance."
