As long as there's something to gain for an aspiring developer by creating a new framework, there will always be churn as there will always be new frameworks. R

As long as there's something to gain for an aspiring developer by creating a new framework, there will always be churn as there will always be new frameworks. Rather than reducing churn we should aspire to make it less and less painful to the point of irrelevance. Some ideas: Standardization of certain APIs (see the craziness in the Javascript world regarding promises, though that night not even matter with 'async')