Difference between revisions of "Gaps in software"

From apm
Jump to: navigation, search
m (Whorf-Conway: added the positive side)
Line 57: Line 57:
 
* [https://en.wikipedia.org/wiki/Concurrent_computing Concurrent computing]  
 
* [https://en.wikipedia.org/wiki/Concurrent_computing Concurrent computing]  
 
* [https://en.wikipedia.org/wiki/Software_transactional_memory Software transactional memory]
 
* [https://en.wikipedia.org/wiki/Software_transactional_memory Software transactional memory]
 +
 +
[[Category:Programming]]

Revision as of 11:43, 11 July 2023

This article is a stub. It needs to be expanded.

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.

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


Gaps in the development of APM

External links

Great article about barriers, gaps, rifts, and plumbing

Whorf-Conway

Combining Whorfs and Conways law ...

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

Concurrency