I don't know, this feels overly vague to me. Sure, some things shouldn't be built with frameworks. However, some things should be. Personally, if the project

I don't know, this feels overly vague to me. Sure, some things shouldn't be built with frameworks. However, some things should be. Personally, if the project is large enough/warrants it, give me rails/django/laravel or ember/angular over something frameworkless _most of the time_. Why? because there is documentation and an established community. With the frameworks I mentioned there is also sometimes conventions (i.e rails/ember). Can you build something with frameworks that is horrific, madding, and complex? Yes. Can you achieve that same result without a framework? Yes. IMO the propensity to get things wrong in the context of a framework is less than the propensity to get things wrong without one. I think this manifesto is missing more thought/detail to properly reason about.