inherent concurrency

electronics -- all electronic components are asynchronous to begin with

Moore’s Law for hardware

no Moore’s Law for software

most current programming languages (e.g. Rust, Python, etc.) are inherently sequential and synchronous

built-in synchrony makes it more difficult to apply ideas like Christopher Alexander’s

sequential operation is required by CPU chips, but, not necessary for human-oriented programming languages

Christopher Alexander’s unstated assumption : units are isolated, asynchronous, pluggable, exchangeable, etc.

https://guitarvydas.github.io/2020/12/09/CALL-RETURN-Spaghetti.html=1

this assumption is not inherently true of software, and, requires work-arounds (aka “epicycles”)

example: PROLOG and relational languages are not sequential and not function based

https://guitarvydas.github.io/2020/12/09/CALL-RETURN-Spaghetti.html&a=1

e.g. full preemption == workaround to allow single notation to be used for all programming