"That which is not tied on will be lost" from [1]
"It should travel with all the things that it needs" from [2]
File:Wirfs-Brock and Wilkerson - 1988 - An Overview of Modular Smalltalk.pdf
Drafts
Opinion
WIP (or Works Not Started), 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 object-functional programming
Thoughts on build tooling (at least most contemporary tools) — The first descriptor I'm inclined to apply is "baroque". More specifically, the systems for building most software, including the requirements of those systems, usually result in a process that is:
inordinate and yet
deficient and unmerciful
Thing is, if you consult the entry for "baroque" in a dictionary or thesaurus], you might come away thinking that, because of the transitive nature of equality, some of these words have an antonymical relationship. Even so, all three are true of most contemporary build systems.