The Problem with Frameworks
Ok, I&#x27;ll take the counterpoint and offer a few challenges I&#x27;ve seen with libraries. In a sense, you are often assembling your own framework. No judgement there--just good to know what you are getting into.<p><pre><code>  - There&#x27;s the potential for quite a bit of choice paralysis along the way as you assemble your stack
  - It&#x27;s harder to seek help: as you&#x27;ve likely assembled a unique collection of tools (and therefore encountered unique challenges)
  - It&#x27;s harder to onboard other developers 
  - There&#x27;s often more bespoke glue code
  - Smaller libraries often have a smaller community and a shorter lifespan
</code></pre>
All of that said, I&#x27;d likely choose the library approach for certain unique applications and the framework approach for &quot;common &#x2F; solved problems&quot; like publishing content.