&gt;&gt; Nope. People should always create and attempt improve upon whats out there.<p>Unless like he states, it causes decision fatigue. What&#x27;s easier? Looking through a small group of well documented and supported frameworks OR trying to a find a decent framework among hundreds of frameworks; many of which, I might add, are either poorly documented or have inherit issues you won&#x27;t discover until you&#x27;re already too deep in your project to change.<p>It&#x27;s interesting to note that in virtually every industry, they realize that giving the customer too many choices leads to fewer sales, less success and leaves them paralyzed and unable to make a decision. Yet, in software development, we firmly believe the exact opposite is true? That somehow giving developers more and more choices is somehow better?<p>Some more support for what I was saying:<p><a href="https:&#x2F;&#x2F;www.gsb.stanford.edu&#x2F;insights&#x2F;research-too-many-choices-can-derail-success" rel="nofollow">https:&#x2F;&#x2F;www.gsb.stanford.edu&#x2F;insights&#x2F;research-too-many-choi...</a><p><i>“People fail to realize that relatively rigid structures can often simplify goal pursuit by removing the need to make choices, especially when people are already well into the process” she says.</i><p><a href="http:&#x2F;&#x2F;www.nytimes.com&#x2F;2010&#x2F;02&#x2F;27&#x2F;your-money&#x2F;27shortcuts.html" rel="nofollow">http:&#x2F;&#x2F;www.nytimes.com&#x2F;2010&#x2F;02&#x2F;27&#x2F;your-money&#x2F;27shortcuts.htm...</a><p><i>That study “raised the hypothesis that the presence of choice might be appealing as a theory,” Professor Iyengar said last year, “but in reality, people might find more and more choice to actually be debilitating.”</i><p><i>Research also shows that an excess of choices often leads us to be less, not more, satisfied once we actually decide. There’s often that nagging feeling we could have done better.</i>