I think the issue comes in to ways:
A company wants people in the same page, so they settle on one approach. This can be ok since most companies probably need one solution.
But a tech company should know many frameworks.
Then there's personal. I think it would take most devs a few years before having the experience required to differentiate and use the right framework for the right tools. And programming moves so fast, some options might no longer be relevant once you're ready
I think the issue comes in to ways:
A company wants people in the same page, so they settle on one approach. This can be ok since most companies probably need one solution.
But a tech company should know many frameworks.
Then there's personal. I think it would take most devs a few years before having the experience required to differentiate and use the right framework for the right tools. And programming moves so fast, some options might no longer be relevant once you're ready
I agree fully with you.
I also think we as a community are following the hype to much.
dev.to itself is written in ruby on rails.
It does not need react hooks or agular X to work good.
It works fine with ruby on rails even if ruby on rails is not the newest hype!