I certainly can appreciate most of this post. I&#x27;ve used so many different frontend (angular, polymer, ExtJS) and backend (express, hapi, restify) frameworks and the various common building tools (grunt, gulp) that it&#x27;s almost impossible to become great at all of them and for a new comer who maybe only used one or two of those frameworks it can be painful getting started.<p>I&#x27;ve started using less and less frameworks as I work on harder and more complex projects. Sometimes I worry I&#x27;m toeing the line at becoming the &quot;old kook who hates new frameworks&quot; but I like things to be explicit and simple; for example if I can write a plain script to handle my build process without integrating grunt or gulp I&#x27;m certainly going to do that.<p>&gt; Leverage folder &amp; file-naming conventions for automatically discovering application-specific routes, actions, tests, and more.<p>Not a fan of this. This is implicit behavior which is almost never intuitive until you&#x27;re experienced in the tooling that has it. I&#x27;d much rather be a tiny bit explicit where there is a list somewhere and I edit that list with patterns or explicit file names. There is no reason there should be &quot;discovery&quot; of such things at _development time_.