I think a big part of the problem is that there are some developers who have been successful in their careers in big tech corporations and are now in leadership roles within those corporations and they think that they know all the answers and are pushing a rigid technical agenda on the rest of the industry. So the situation is that there are a bunch of lottery winners who think that because they won a lottery, they're qualified to tell everyone else what to do. But in reality, the lottery winners know less about reality because they took the easy road. The reality is that 99% of the time, there is no easy road to take; there are no silver bullets.

In the old days, developers could choose what frameworks or tools they wanted to use for specific projects. There was a lot of flexibility. Nobody would be shunned for choosing a niche framework or tool if they could justify it. Many companies created their own frameworks and that often worked out fine.

Nowadays, when companies are hiring, they expect developers to know an increasingly long and specific list of increasingly opinionated tools and frameworks. It removes a lot of flexibility from the job and, more often then then not, it leads to sub-optimal results and it encourages high staff turnover (since many big companies use the same popular frameworks; employees can easily move between these companies). There is no feeling of being part of a 'team' anymore due to the extreme staff turnover in the industry.