Generally speaking, having multiple choice isn't a bad thing. The real problem is that every time a famework gains a bit of momentum, it's very often depicted as the promised land for the Web Developer.
It may be, or it may not, so if you have to choose which framework to use, you may get into trouble if you listen only to the hype of the moment.
I think that no one nowadays could question about Angular success, but when Angular was released, it was as a bet as other frameworks, like Meteor, for example, a really promising framework I don't hear talking about anymore.
Another problem is that getting acquainted with a frameworks requires time , practice and experience, and in a world were evolution of technology runs really really fast it's not so easy.
Luckily, most of the frameworks do have a lot common factors, and I think a good developer should focus to learn these common factors, and to learn them well. This way, shifting from framework 'A' to framework 'B' should not be an hell.
I'm not dead! I feel happy! I'd like to go for a walk! I'll even read a tiny ad: