Library patterns: Why frameworks are evil
<p><pre><code>  This follows from my experience with building F# libraries, but the ideas are quite general and can be useful in any programming language.
</code></pre>
This is just not true. The whole article really doesn&#x27;t apply to any mainstream programming languages like ruby, python, java, javascript etc. The author seems to be coming from an academic view point and the points he makes really don&#x27;t translate to the software engineering world.<p>His analogy about frameworks being package holidays while composing libraries is like independent travel only tells half the story. How do you organise the interaction of libraries? You can do it yourself but you will have to follow some sort of pattern to organise the code in order to make it easy to work with. What happens when another coder joins your project? Are you going to tell them the pattern you have already been using? What if they dont follow it as expected or disagree with it? Frameworks standardise this. Yes you might not always like certain aspects of the framework you&#x27;re using but its the price you pay for not having a project full of developers who each have their own way of doing things and are constantly argueing over how to organise the codebase.<p>Also this hyperbolic use of the word &quot;evil&quot; is immature and dorky. Sorry.