My understanding is that TLA+ is for concurrent applications, but with a broad definition of "concurrent." For example, it could be...
* multiple hosts messaging each other
* multiple threads in one process sharing a data structure
* multiple API calls that all use the same Postgres DB
In other words, any sort of system where different actors can step on each others' toes.
Non-determinism might be a better thing to anchor the value to. For example in a deterministic "normal" programming environment, an if/then/else statement will execute only one out of two possible code paths. You have to run the code with a complementary condition to observe the other code path.
In a non-deterministic environment like TLA+ both possible code paths are executed. You can observe state transitions in both possibilities.
In a deterministic context the combinatorics of code paths can get out of hand quickly. Non-deterministically you have one set of assertions for all code paths, or patterns of paths.
Summarizing:
- Italians in the North are less prone to lactose malabsorption than those in the South - They don't drink cappuccinos after 11 because it's heavy to digest - The video includes some information about why milk is hard to digest, and other things
Some non-snarky comments provided some really good counter examples, eg they eat ice cream all afternoon.
Also from my own experience in the south: every morning kids eat a bowl of milk with a shot of espresso over cereal.
* RH feels like accepting a TOS or a EULA; * E-Trade makes it that you are reporting net-worth and are willing to risk it.
Can RH be held liable for misrepresenting the regulations? This might have been settled without any loss of life.
He writes my favorite books.