Gaps in software

• RAM to HDD serializarion barrier
• The CPU GPU gap
• inter process communication barrier
• network serialization barrier
• GUI commandline rift
• (Caches-level barriers)
• value-level type-level barrier – dependently typed languages try to solve this one

---

• Safe cross thread communication in concurrent computing

Related

• The problem with current day programming and its causes
• General software issues
• Software

---

• Potentially solving a lot of the rifts: content addressed approach

---

• Bridging the gaps in the development of advanced productive nanosystems

External links

• Serialization
• Inter-process communication

About barriers, gaps, rifts, and plumbing

• The future of software, the end of apps, and why UX designers should care about type theory – by Paul Chiusano 2013-05-22 – plumbing

Combining Whorfs and Conways law

• Linguistic relativity (Sapir–Whorf hypothesis) – "the structure of a language affects its speakers' worldview or cognition" (and what we they express)
• Conway's law – "organizations design systems that mirror their own communication structure"

Adding both of the above together one can get the following:
Bad (programming) "languages" for human computer communication limits what we can express (Saphir-Whorf).
This is a limit on our communication structure, and ultimately leads to bad systems being built (Conway).

Concurrency

• Concurrent computing
• Software transactional memory