• A transactional way to program concurrently defines a declarative structure of atomic blocks
  • The atomic construct is declarative: the programmer states what to do (maintain atomicity of this block of code), not how to do it; no explicit use or management of locks
  • System implements synchronization as necessary to ensure atomicity: system could implement atomic{} using locks, but the transactional implementation uses optimistic concurrency, maintaining serialization only in situations of true contention (R-W or W-W conflicts)

Was pretty interested in this distinction of "programming paradigms". And I was curious to know whether there even exist frameworks/languages which follow a declarative paradigm. Turns out React.js is a great example of this. Code in React does not directly change any element or alter the state of the execution, it merely indicates what needs to be done by the program somehow.

To read up more: https://codeburst.io/declarative-vs-imperative-programming-a8a7c93d9ad2

Which type of abstractions is most common in the workforce?