Holy Things in Computing - Revision history

ViciousCarnivore at 04:51, 18 January 2026

2026-01-18T04:51:54Z

2026-01-08T09:09:41Z

2026-01-08T09:09:07Z

2026-01-08T09:08:34Z

2025-11-13T00:37:54Z

2024-10-26T14:28:13Z

2024-10-26T14:27:34Z

2024-10-26T14:27:10Z

2024-10-26T14:26:08Z

2024-10-26T14:25:55Z

← Older revision		Revision as of 04:51, 18 January 2026
Line 42:		Line 42:
	* Shared repositories. (i.e. a single LLM database, where everyone can access it) (somewhat of a repeat of above, but I'm referring to the LLM industry).		* Shared repositories. (i.e. a single LLM database, where everyone can access it) (somewhat of a repeat of above, but I'm referring to the LLM industry).
	* Peer 2 Peer (P2P) software. Bittorrent, is a good example of successful P2P software.		* Peer 2 Peer (P2P) software. Bittorrent, is a good example of successful P2P software.
		+	* Using the file system to store data in a readable format (i.e. maildir). The opposite of this, which is bad design, is an mbox.

@@ Line 40: / Line 40: @@
 </pre>
 * when a program fails, it must warn the user (it should never fail silently)
-* Shared repositories. (i.e. a single LLM database, where everyone can access it).
+* Shared repositories. (i.e. a single LLM database, where everyone can access it) (somewhat of a repeat of above, but I'm referring to the LLM industry).
 * Peer 2 Peer (P2P) software. Bittorrent, is a good example of successful P2P software.

@@ Line 41: / Line 41: @@
 * when a program fails, it must warn the user (it should never fail silently)
 * Shared repositories. (i.e. a single LLM database, where everyone can access it).
-* Peer 2 Peer software
+* Peer 2 Peer (P2P) software. Bittorrent, is a good example of successful P2P software.

← Older revision		Revision as of 09:08, 8 January 2026
Line 40:		Line 40:
	</pre>		</pre>
	* when a program fails, it must warn the user (it should never fail silently)		* when a program fails, it must warn the user (it should never fail silently)
		+	* Shared repositories. (i.e. a single LLM database, where everyone can access it).
		+	* Peer 2 Peer software

← Older revision		Revision as of 00:37, 13 November 2025
Line 39:		Line 39:
	└─udevd		└─udevd
	</pre>		</pre>
		+	* when a program fails, it must warn the user (it should never fail silently)

@@ Line 13: / Line 13: @@
 * repositories of basic files. i.e. places where you can visit and get say:
 Random images, random text files, random movies. random songs. A combination of randomness with
-common media types. Sometimes they are geared to a subject (i.e. rock music, anime images). but no fluff, just the media. An example would be https://safebooru.org/ and https://danbooru.donmai.us/
+common media types. Sometimes they are geared to a subject (i.e. rock music, anime images). but no fluff, just the media. An example would be https://safebooru.org/ and https://danbooru.donmai.us/ We need more websites like this.
 * repos of programs
 * this:

@@ Line 26: / Line 26: @@
 * network monitoring
 * cpu / ram monitoring of a program as development progresses, tracing, profiling
-* computer instruction repositories / search engines (rosetta code https://rosettacode.org/wiki/Rosetta_Code)
+* computer instruction repositories / search engines (https://rosettacode.org/wiki/Rosetta_Code)
 * when you can list all the processes running, and they dont overflow the screen (this is another simplicity)
 <pre>