User:Colby Russell: Difference between revisions

Content added Content deleted

Inline

Latest revision as of 21:56, 12 March 2023

"The greatest performance improvement of all is when a system goes from not-working to working" from [1]

"[This] is software design on the scale of decades: every detail is intended to promote software longevity and independent evolution. Many of the constraints are directly opposed to short-term efficiency." from [2]

"That which is not tied on will be lost" from [3]

"It should travel with all the things that it needs" from [4]

File:Wirfs-Brock and Wilkerson - 1988 - An Overview of Modular Smalltalk.pdf

They might never tell you it's broken

Code that doesn't rot

Drafts[edit]

Opinion[edit]

Tight coupling over fragile links is one of the industry's biggest problems right now. Tight coupling and fragile links are enemies.

Additionally, for all the inroads that are made in increasing the power of software, there is a phantom contingent whose work has the effect (even without the explicit intent) of keeping computing and general software development inaccessible instead of more accessible. This type of obscurantism is a form of gatekeeping and needs to be minimized.

Other WIP (or Works Not Started; position papers), in first person:

The case for the triple script module system
The case for accepting the W3C–WHATWG hypertext system as the universal medium, aka "Browsers, builds, and burdens"—the basic thrust being, "The WWW is an acceptable NLS"
The case for object-functional programming

Notes[edit]

(NB: There's a reason why these pages are called "Notes" and live in my personal namespace. You are not expected to be impressed by or receptive to anything here. In fact, best not to even look at these. There's a whole wiki to peruse and interesting papers linked above, instead.)

@@ Line 1: / Line 1: @@
+"The greatest performance improvement of all is when a system goes from not-working to working" from [https://web.stanford.edu/~ouster/cgi-bin/sayings.php]
+"[This] is software design on the scale of decades: every detail is intended to promote software longevity and independent evolution. Many of the constraints are directly opposed to short-term efficiency." from [https://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven#comment-724]
 [https://graph.global/?id=1347 "That which is not tied on will be lost"] from [https://michaelkarpeles.com/curations/life-lessons#sec-2]
@@ Line 4: / Line 8: @@
 [[File:Wirfs-Brock and Wilkerson - 1988 - An Overview of Modular Smalltalk.pdf]]
+[https://pointersgonewild.com/2019/11/02/they-might-never-tell-you-its-broken/ They might never tell you it's broken]
+[https://pointersgonewild.com/2022/02/11/code-that-doesnt-rot/ Code that doesn't rot]
 == Drafts ==
@@ Line 12: / Line 20: @@
 == Opinion ==
+Tight coupling over fragile links is one of the industry's biggest problems right now.  Tight coupling and fragile links are enemies.
-'''WIP''' (or '''Works Not Started'''), in first person:
+Additionally, for all the inroads that are made in increasing the power of software, there is a phantom contingent whose work has the ''effect'' (even without the explicit intent) of keeping computing and general software development inaccessible instead of more accessible.  This type of obscurantism is a form of gatekeeping and needs to be minimized.
+Other '''WIP''' (or '''Works Not Started'''; position papers), in first person:
 * The case for the triple script module system
-* The case for accepting the W3C–WHATWG hypertext system as the universal medium, aka "Browsers, builds, and burdens"
+* The case for accepting the W3C–WHATWG hypertext system as the universal medium, aka "Browsers, builds, and burdens"—the basic thrust being, "The WWW is an acceptable [https://en.wikipedia.org/wiki/NLS_(computer_system) NLS]"
-* The case for object-functional programming
+* The case for object-functional programming <!-- some discussion here https://news.ycombinator.com/item?id=30293622 -->
 == Notes ==
+(NB: There's a reason why these pages are called "Notes" and live in my personal namespace.  You are not expected to be impressed by or receptive to anything here.  In fact, best not to even look at these.  There's a whole wiki to peruse and interesting papers linked above, instead.)
 * [[User:Colby Russell/Pitches]]
@@ Line 27: / Line 41: @@
 * [[User:Colby Russell/JS bridge]]
 * [[User:Colby Russell/Object builder]]
+* [[User:Colby Russell/Composability]]
+* [[User:Colby Russell/Hedging]]
+* [[User:Colby Russell/Limits]]
+* [[User:Colby Russell/Deploy.app.htm]]
+* [[User:Colby Russell/Every module a program]]
+* [[User:Colby Russell/Non-uniform build scripts]]
+* [[User:Colby Russell/Debugging]]