Difference between revisions of "Gaps in software"
From apm
m (→Related) |
(added explanatory intro – why it is important) |
||
| Line 1: | Line 1: | ||
{{stub}} | {{stub}} | ||
| − | * RAM to HDD | + | With the development of [[atomically precise manufacturing]] we'll <br> |
| + | eventually reach [[a future world where matter essentially becomes software]]. <br> | ||
| + | So it is really important to fix all the cracks and gaps within software till then. <br> | ||
| + | Heck, if problems are not fixed there will be serious problems long before <br> | ||
| + | [[advanced productive nanosystem]]s arrive. | ||
| + | |||
| + | == List of gaps / cracks / rifts / barriers /... == | ||
| + | |||
| + | * RAM to HDD serialization barrier | ||
* The CPU GPU gap | * The CPU GPU gap | ||
* inter process communication barrier | * inter process communication barrier | ||
| Line 10: | Line 18: | ||
---- | ---- | ||
* Safe cross thread communication in concurrent computing | * Safe cross thread communication in concurrent computing | ||
| + | |||
| + | These gaps can be underlying causes for higher up manifesting symptoms ... | ||
== Related == | == Related == | ||
| Line 18: | Line 28: | ||
---- | ---- | ||
* Potentially solving a lot of the rifts: [[content addressed]] approach | * Potentially solving a lot of the rifts: [[content addressed]] approach | ||
| − | + | ||
| + | === Gaps in the development of [[APM]] === | ||
| + | |||
* '''[[Bridging the gaps]]''' in the development of [[advanced productive nanosystem]]s | * '''[[Bridging the gaps]]''' in the development of [[advanced productive nanosystem]]s | ||
| Line 26: | Line 38: | ||
* [https://en.wikipedia.org/wiki/Inter-process_communication Inter-process communication] | * [https://en.wikipedia.org/wiki/Inter-process_communication Inter-process communication] | ||
| − | === | + | === Great article about barriers, gaps, rifts, and plumbing === |
* [https://pchiusano.github.io/2013-05-22/future-of-software.html The future of software, '''the end of apps''', and why UX designers should care about type theory – by Paul Chiusano 2013-05-22] – plumbing | * [https://pchiusano.github.io/2013-05-22/future-of-software.html The future of software, '''the end of apps''', and why UX designers should care about type theory – by Paul Chiusano 2013-05-22] – plumbing | ||
Revision as of 17:04, 16 July 2021
With the development of atomically precise manufacturing we'll
eventually reach a future world where matter essentially becomes software.
So it is really important to fix all the cracks and gaps within software till then.
Heck, if problems are not fixed there will be serious problems long before
advanced productive nanosystems arrive.
Contents
List of gaps / cracks / rifts / barriers /...
- RAM to HDD serialization 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
These gaps can be underlying causes for higher up manifesting symptoms ...
Related
- Potentially solving a lot of the rifts: content addressed approach
Gaps in the development of APM
- Bridging the gaps in the development of advanced productive nanosystems
External links
Great article 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).
