Gaps in software

Up: Software trouble pages

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. Also gradually typed ones?
  A related topic is: Interleaving edit, compile, and runtime

---

• Safe cross thread communication in concurrent computing

---

Domain specific languages DSLs:

• DSL to general purpouse programming language barrier
  Having a DSL as a library is highly desired but then
  there still can be a DSL to host language barrier
  related to homoiconicity

Why these gaps are highly problematic, damaging, and harmful

– Losing stability from lack of stable links in a large ad-hock patchwork of tools, getting fragility and rapid bit-rot instead. – Losing terseness and localness staying in a single programming language,
instead getting verboseness, overwhelming complexity from idiosyncrasies of a patchwork of very many tools (Rube Goldberg machine). Also one gets lots (too many) of nontrivial to trace indirections. – Losing guarantees given by a good programming language like e.g. type safety

All this drives up cost of production and worse cost of maintenance of code and software.
Software creators increasingly become the slave of their own creation falling apart ever more rapidly if unattended.
Likely a reason why free and open source software (not funded by crypto gambing) is increasingly in a crisis.
And why the (to the authors view) false dichotomy "If you don't pay you are the product." gets
increasingly lifted up to harmful(?) gospel.
End of rant.

Related

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

---

• 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

• Serialization
• Inter-process communication

Great article 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

Whorf-Conway

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/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

• Concurrent computing
• Software transactional memory

Gaps in SW due to low level techinical challenges & high level social challenges

Technical

A rant on Rube Goldberg software framework plumbing and app(lication)s being closed of silos:
The future of software, the end of apps, and why UX designers should care about type theory – by Paul Chiusano 2013-05-22

Social

Beside that there are gaps that will be eternally again and again recreated due to
governance across the internet being not yet solved and thus distrust being the default leading to
artificial security sandboxing barriers being erected again and again.

Best effort to solve internet governance problem (highly nontrivial technical solution for a huge social problem)
that APM:About has seen so far (2024) is holochain.
Or more generally some of the principles of that the holochain protocol project pursues.
Specifically the part about
cross community (today cross platform) migratable self-souvereingn reputations
(a subset of self souvereign identity SSID)
and from these a buildup of a network of trust (partly via gossiping partly higher level).
That plus zero knowledge proofs allowing to reveal only parts of ones identity that are required and one is willing to share.
The CAL cryptrograpic autonomy license was (for one thing) created to enforce souvereignity (and thus transferability)
of ones reputation and other aspects of identity.
[Cryptographic Autonomy License Version 1.0 – on OSI website]