Gaps in software: Difference between revisions
Jump to navigation
Jump to search
→Related: added * Bridging the gaps in the development of advanced productive nanosystems |
m →Related |
||
| Line 15: | Line 15: | ||
* [[The problem with current day programming and its causes]] | * [[The problem with current day programming and its causes]] | ||
* [[General software issues]] | * [[General software issues]] | ||
* [[Software]] | * '''[[Software]]''' | ||
---- | ---- | ||
* Potentially solving a lot of the rifts: [[content addressed]] approach | * Potentially solving a lot of the rifts: [[content addressed]] approach | ||
Revision as of 16:53, 16 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
Related
- Potentially solving a lot of the rifts: content addressed approach
- Bridging the gaps in the development of advanced productive nanosystems
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).