Theres Always a Framework
From Zanecorpwiki
By the operational definition of frameworks, every product must exist within a framework.
The first implication is ontological. Something is always preceded by something, never by nothing. Time precedes time.[notes 1] In the most general sense, we are saying that meaning without context is a rational contradiction.
This is very clear in software. A web page exists within a framework of Rails. Rails is exists within a framework of Ruby. There are implementations of Ruby-as-a-specification created within the frameworks of both Java and C. The Ruby specification exists within a conceptual framework that blends Perl, Python, and Lisp. The implementation and conceptual frameworks each continue back, branching and coalescing all the way the framework of the physical machine, discrete math, and the Turing theory of computation.
Any craftsman sufficiently advanced in the understanding of their field can, to some extent, visualize and understand the field as a tapestry of interlocked and overlapping frameworks. It is the nature of frameworks that the work from within is (or at least should be) simple, but that does not preclude a knowledgeable craftsman from taking a cross section of the black box even as they operate from within and wondering at the intricacies of the system even as we concentrate on the task at hand.
Notes
- ↑ This is not to say that there may not be some "base reality" to things in some sense, but it does assert that such a reality, in which there is no "containing reality" has no meaning within the current universe of discourse. Time before time is inaccessible and moot as far as the rational discussion goes. The nature of base reality and non-time are matters of faith. Not unreasonable, but they are without reason.
