In terms of capabilities they are fairly similar but the the existence of an official router and official state management store means that the "things that can break in horrible ways" surface is reduced.
I stuck with KnockoutJS for a long time because they had (for a JavaScript project) incredible backwards compatibility and stability.
I've been programming long enough that "the new hotness" is of much lower interest than "what capability does it give me I don't have and will I still be able to build/deploy this in 3 years if I need to".
Also if something seems amazing I'll wait a year, if it was amazing it'll still be amazing in a year and I'll have 365 days of other people smacking their heads on the not amazing parts.
Someone else I know also has a soft spot for Ember though from my vantage point (dabbled in them all), they all seem quite similar. (Them being Ember, Backbone, Angular).
React, in my opinion, is filled with "best practices" where they choose complex solutions to simple problems. The dependency hell is also ridiculous in React. I would like to see how many of these apps are having issues upgrading to the latest versions of their dependencies in 5 years.