For sure there is a reason why Google, Facebook, etc. produced those frameworks, but it was never "let's build a framework to help (unexperienced) developers". It always started as what I describe: a framework developed to fit an app. Then it was generalized to meet other purposes, and so it led to this “general-purpose framework” anti-pattern, as one size never fits all. As a collateral damage, it made young developers believe that this was *the way* to develop apps (thus forging the "law of instrument"), that it will save time, etc.

Currently I save time and improve by *not* using framework, but I have to admit that my seniority (knowledge of patterns, not falling in my past traps) helps for that. But hey, you have to start learning at some point. Some real, long-term knowledge that can be leveraged in various context, not only a given framework.