Moreover, Backbone is a great example of MVC, the understanding of which is useful and highly transferrable to other (even non-JS) frameworks.
Also, React Native is the new way they're proposing to build native mobile apps; definitely new but worth it to learn React in case this works out.
I would definitely push people towards learning Meteor. I know it's a full stack framework instead of just a front end framework but for rapid prototyping, it's fantastic. The community for Meteor is a bit hit or miss because it's so "magical" but it's worth a look too.
Disclaimer: I've only ever done about a week of Angular so I cannot compare features.
It is more like:
* React
* React-Router
* JQuery (for the AJAX functionality)
* A library for or to help build Observables like EventEmitter, RxJS, or BaconJS
* Immutable.js is useful in many projects
There are also many patterns that have cropped up with React like Flux or Container-Component.
For a newbie, getting started with Angular is much easier.
React doesn't need a router for many uses (extending existing sites), but does need lodash/ramda and an AJAX library. ImmutableJS is useful for both angular and react (as is rxjs/baconjs). For a beginner, I would simply say React, Reflux, Ramda, and jQuery will do 90% of the things. Learning all four of these libraries (they probably already know jQuery) will take less time than Angular and be more flexible if they want to swap one out later.
Finally, adding these is much easier with commonJS than the angular dependency injection (often on top of commonJS).
Angular: http://www.letscodejavascript.com/v3/blog/2015/01/angular_re...
React: http://www.letscodejavascript.com/v3/blog/2014/09/react_revi...
I've also heard good things about Knockout, but I haven't reviewed it. Ember is also popular; I've used it and prefer React.
Some people will say that it's unfair comparison because React does so much less than Ember and Angular. To that I can only say: Yes, and that's part of why it's better.
After using it for a few years, "passive-aggressive architecture" really is the best way to refer to it.