Difference between revisions of "Gaps in software"
From apm
(added value-level type-level barrier) |
(added * The CPU GPU gap) |
||
| Line 2: | Line 2: | ||
* RAM to HDD serializarion barrier | * RAM to HDD serializarion barrier | ||
| + | * The CPU GPU gap | ||
* inter process communication barrier | * inter process communication barrier | ||
* network serialization barrier | * network serialization barrier | ||
Revision as of 14:08, 13 July 2021
- 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
Contents
Related
- Potentially solving a lot of the rifts: content addressed approach
External links
About barriers, gaps, rifts, and 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).
