Gaps in software - Revision history

Apm: /* Gaps in SW due to low level techinical challenges & high level social challenges */ typofix

2025-09-05T03:05:51Z

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

← Older revision		Revision as of 05:05, 5 September 2025
Line 37:		Line 37:
	'''End of rant.'''		'''End of rant.'''

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

	== Technical ==		== Technical ==

Apm: all headlines one level up

2025-06-18T06:44:16Z

all headlines one level up

Apm: /* External links */

2024-05-06T10:29:05Z

External links

← Older revision		Revision as of 12:29, 6 May 2024
Line 89:		Line 89:
	* [https://en.wikipedia.org/wiki/Serialization Serialization]		* [https://en.wikipedia.org/wiki/Serialization Serialization]
	* [https://en.wikipedia.org/wiki/Inter-process_communication Inter-process communication]		* [https://en.wikipedia.org/wiki/Inter-process_communication Inter-process communication]
			* [https://opensource.org/license/cal-1-0 Cryptographic Autonomy License Version 1.0 – on OSI website]

	=== Great article about barriers, gaps, rifts, and plumbing ===		=== Great article about barriers, gaps, rifts, and plumbing ===

Apm: /* Social */

2024-05-06T10:28:44Z

Social

← Older revision		Revision as of 12:28, 6 May 2024
Line 60:		Line 60:
	The CAL cryptrograpic autonomy license was (for one thing) created to enforce souvereignity (and thus transferability) <br>		The CAL cryptrograpic autonomy license was (for one thing) created to enforce souvereignity (and thus transferability) <br>
	of ones reputation and other aspects of identity. <br>		of ones reputation and other aspects of identity. <br>
	[[https://opensource.org/license/cal-1-0 Cryptographic Autonomy License Version 1.0 – on OSI website]] <br>		[https://opensource.org/license/cal-1-0 Cryptographic Autonomy License Version 1.0 – on OSI website] <br>

	== Whorf-Conway (in a) cycle 🔁 ==		== Whorf-Conway (in a) cycle 🔁 ==

Apm: /* Great article about barriers, gaps, rifts, and plumbing */

2024-05-06T10:28:13Z

Great article about barriers, gaps, rifts, and plumbing

← Older revision		Revision as of 12:28, 6 May 2024
Line 92:		Line 92:
	=== Great article about barriers, gaps, rifts, and plumbing ===		=== 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 – [https://web.archive.org/web/20240318120002/http://pchiusano.github.io/2013-05-22/future-of-software.html (same via internetarchive)]

	=== Concurrency ===		=== Concurrency ===

Apm at 10:13, 5 May 2024

2024-05-05T10:13:27Z

← Older revision		Revision as of 12:13, 5 May 2024
Line 36:		Line 36:
	increasingly lifted up to harmful(?) gospel. <br>		increasingly lifted up to harmful(?) gospel. <br>
	'''End of rant.'''		'''End of rant.'''

	~~=== Gaps in the development of [[APM]] ===~~

	* '''[[Bridging the gaps]]''' in the development of [[advanced productive nanosystem]]s

	== Gaps in SW due to low level techinical challenges & high level social challenges ==		== Gaps in SW due to low level techinical challenges & high level social challenges ==
Line 84:		Line 80:
	----		----
	* 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

	== External links ==		== External links ==

Apm: moved section == Related == down again

2024-05-05T10:11:55Z

moved section == Related == down again

@@ Line 36: / Line 36: @@
 increasingly lifted up to harmful(?) gospel. <br>
 '''End of rant.'''
 === Gaps in the development of [[APM]] ===
@@ Line 74: / Line 66: @@
 [[https://opensource.org/license/cal-1-0 Cryptographic Autonomy License Version 1.0 – on OSI website]] <br>
-== External links ==
+== Whorf-Conway (in a) cycle 🔁 ==
 Combining Whorfs and Conways law. Very briefly the laws are:
@@ Line 93: / Line 76: @@
 * This is a limit on (or enhancement of) our communication structure, and ultimately leads to worse/better (programming) "systems" being built (Conway).
 Somewhat loose interpretation but perhaps interesting.
 === Concurrency ===

Apm: chapter reorder putting external links bottom again & edits to === Whorf-Conway (in a) cycle 🔁 ===

2024-05-05T10:09:18Z

chapter reorder putting external links bottom again & edits to === Whorf-Conway (in a) cycle 🔁 ===

@@ Line 48: / Line 48: @@
 * '''[[Bridging the gaps]]''' in the development of [[advanced productive nanosystem]]s
 == Gaps in SW due to low level techinical challenges & high level social challenges ==
@@ Line 98: / Line 73: @@
 of ones reputation and other aspects of identity. <br>
 [[https://opensource.org/license/cal-1-0 Cryptographic Autonomy License Version 1.0 – on OSI website]] <br>
 [[Category:Programming]]
 [[Category:Software]]

Apm: /* Why these gaps are highly problematic, damaging, and harmful */ some cleanup

2024-05-05T09:55:36Z

Why these gaps are highly problematic, damaging, and harmful: some cleanup

← Older revision		Revision as of 11:55, 5 May 2024
Line 25:		Line 25:
	== Why these gaps are highly problematic, damaging, and harmful ==		== 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 stability from lack of stable links in a large ad-hock patchwork of tools (that typically know little of each other). <br>Getting fragility and rapid bit-rot instead.
	* Losing terseness and localness staying in a single programming language~~, instead~~ getting verboseness, <br>overwhelming complexity from idiosyncrasies of a patchwork of very many tools (Rube Goldberg machine). <br>Also one gets lots (too many) of nontrivial to trace indirections.		* Losing terseness and localness staying in a single programming language. Instead getting verboseness, <br>overwhelming complexity from idiosyncrasies of a patchwork of very many tools (Rube Goldberg machine). <br>Also one gets lots (too many) of nontrivial to trace indirections.
	* Losing guarantees given by a good programming language like e.g. type safety and referential transparency (see: [[Purely functional programming]])		* Losing guarantees given by a good programming language <br>like e.g. type safety and guarantees on referential transparency <br>(see: [[Purely functional programming]]). <br>Instead getting heisenbugs and silent very hard to reproduce runtime type errors.
			* There is likely more missed in this listing here.

	'''All this drives up cost of production and worse cost of maintenance of code and software.''' <br>		'''All this drives up cost of production and worse cost of maintenance of code and software.''' <br>

Apm: /* Why these gaps are highly problematic, damaging, and harmful */ bullet points, line-breaks, & link to Purely functional programming

2024-05-05T09:51:39Z

Why these gaps are highly problematic, damaging, and harmful: bullet points, line-breaks, & link to Purely functional programming

← Older revision		Revision as of 11:51, 5 May 2024
Line 25:		Line 25:
	== Why these gaps are highly problematic, damaging, and harmful ==		== 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 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, ~~<br>~~ 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 terseness and localness staying in a single programming language, instead getting verboseness, <br>overwhelming complexity from idiosyncrasies of a patchwork of very many tools (Rube Goldberg machine). <br>Also one gets lots (too many) of nontrivial to trace indirections.
	– Losing guarantees given by a good programming language like e.g. type safety		* Losing guarantees given by a good programming language like e.g. type safety and referential transparency (see: [[Purely functional programming]])

	'''All this drives up cost of production and worse cost of maintenance of code and software.''' <br>		'''All this drives up cost of production and worse cost of maintenance of code and software.''' <br>

← Older revision		Revision as of 08:44, 18 June 2025
Line 8:		Line 8:
	[[advanced productive nanosystem]]s arrive.		[[advanced productive nanosystem]]s arrive.

	== List of gaps / cracks / rifts / barriers /... ==		= List of gaps / cracks / rifts / barriers /... =

	* RAM to HDD serialization barrier		* RAM to HDD serialization barrier
Line 23:		Line 23:
	* [[DSL to general purpouse programming language barrier]] <br> Having a [[DSL as a library]] is highly desired but then <br>there still can be a [[DSL to host language barrier]] <br>related to [[homoiconicity]]		* [[DSL to general purpouse programming language barrier]] <br> Having a [[DSL as a library]] is highly desired but then <br>there still can be a [[DSL to host language barrier]] <br>related to [[homoiconicity]]

	== Why these gaps are highly problematic, damaging, and harmful ==		= Why these gaps are highly problematic, damaging, and harmful =

	* Losing stability from lack of stable links in a large ad-hock patchwork of tools (that typically know little of each other). <br>Getting fragility and rapid bit-rot instead.		* Losing stability from lack of stable links in a large ad-hock patchwork of tools (that typically know little of each other). <br>Getting fragility and rapid bit-rot instead.
Line 37:		Line 37:
	'''End of rant.'''		'''End of rant.'''

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

	=== Technical ===		== Technical ==

	A rant on Rube Goldberg software framework plumbing and app(lication)s being closed of silos: <br>		A rant on Rube Goldberg software framework plumbing and app(lication)s being closed of silos: <br>
	[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		[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

	=== Social ===		== Social ==

	Beside that there are gaps that will be eternally again and again recreated due to <br>		Beside that there are gaps that will be eternally again and again recreated due to <br>
Line 62:		Line 62:
	[https://opensource.org/license/cal-1-0 Cryptographic Autonomy License Version 1.0 – on OSI website] <br>		[https://opensource.org/license/cal-1-0 Cryptographic Autonomy License Version 1.0 – on OSI website] <br>

	== Whorf-Conway (in a) cycle 🔁 ==		= Whorf-Conway (in a) cycle 🔁 =

	Combining Whorfs and Conways law. Very briefly the laws are:		Combining Whorfs and Conways law. Very briefly the laws are:
Line 73:		Line 73:
	Somewhat loose interpretation but perhaps interesting.		Somewhat loose interpretation but perhaps interesting.

	== Related ==		= Related =

	* [[The problem with current day programming and its causes]]		* [[The problem with current day programming and its causes]]
Line 81:		Line 81:
	* 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]] ===		== 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

	== External links ==		= External links =

	* [https://en.wikipedia.org/wiki/Serialization Serialization]		* [https://en.wikipedia.org/wiki/Serialization Serialization]
Line 91:		Line 91:
	* [https://opensource.org/license/cal-1-0 Cryptographic Autonomy License Version 1.0 – on OSI website]		* [https://opensource.org/license/cal-1-0 Cryptographic Autonomy License Version 1.0 – on OSI website]

	=== Great article about barriers, gaps, rifts, and plumbing ===		== 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://web.archive.org/web/20240318120002/http://pchiusano.github.io/2013-05-22/future-of-software.html (same via internetarchive)]		* [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://web.archive.org/web/20240318120002/http://pchiusano.github.io/2013-05-22/future-of-software.html (same via internetarchive)]

	=== Concurrency ===		== Concurrency ==

	* [https://en.wikipedia.org/wiki/Concurrent_computing Concurrent computing]		* [https://en.wikipedia.org/wiki/Concurrent_computing Concurrent computing]