Why position Commonware as Framework rather than a Library? #234
-
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Really appreciate you taking the time to elaborate on the nuance, in your experience, between a Framework and Library. Your assessment of a Framework's limitations (by design) are exactly what I'm trying to avoid with the design of the primitives I'm working on. In hindsight, I fear I "named" the collection of primitives without appreciating what "Framework" implies (thinking of SDK, Framework, Library, etc as "loose synonyms"). This is why they used to never let me brand anything (not a lot of fans of Vilmo, Vena, Vryx lol). I'll ponder this for a bit but strongly agree with your view and don't want to imply something I don't mean (I have a feeling the "framework" moniker might not be long for this project...) |
Beta Was this translation helpful? Give feedback.
-
|
After sleeping on this, I agree with your assessment and am changing the wording from Framework -> Library. |
Beta Was this translation helpful? Give feedback.
Really appreciate you taking the time to elaborate on the nuance, in your experience, between a Framework and Library. Your assessment of a Framework's limitations (by design) are exactly what I'm trying to avoid with the design of the primitives I'm working on.
In hindsight, I fear I "named" the collection of primitives without appreciating what "Framework" implies (thinking of SDK, Framework, Library, etc as "loose synonyms"). This is why they used to never let me brand anything (not a lot of fans of Vilmo, Vena, Vryx lol).
I'll ponder this for a bit but strongly agree with your view and don't want to imply something I don't mean (I have a feeling the "framework" moniker might not be lo…