Give it a year or so.
What's happening with React is different though, and happens only once in a very long while: engineering complexities that seem to have spun wildly out of control become radically simplified by something sitting right under your nose.
It's exciting. Congrats to all of those who have contributed to React.
There's very little to understand, it's really really simple.
With React, I don't really see the point of Ember or Angular, they're basically zombie projects now. I wonder how their devs feel about React. React is an evolutionary leap enabled by their shadow DOM technology. Being able to rerender the whole page in a millisecond is a game changer.
React only deals with the view. In AngularJS, third party objects have a seamless integration with the view.
Imagine you want to paginate datas.
You'd write a Paginator component in React.
In Angular you'd have a Paginator service holding pagination logic. Then you can have multiple representations of paginators,that would be logic less. It's better because it makes it easier to test the pagination logic in isolation,and you can then hide some complexity out of the view.
i did it with a simple notification queue in a project i'm working on :
.service('Notification', function($timeout, NOTIFICATION_TIME) {
/**
* manage notifications
*/
var onNotificationTimeEnd ;
this.type = {
'SUCCESS': 'text-success',
'ERROR': 'text-error',
'INFO': 'text-info'
};
this.timeout = null;
this.current = null;
this.notifications=[];
/**
* queue app notifications
* @param {Object} notif
*/
this.notify = function(notif) {
if(notif){
this.notifications.push(notif);
}
if(!this.current){
this.current = this.notifications.pop();
}
if(!this.timeout){
this.timeout=$timeout(onNotificationTimeEnd.bind(this), NOTIFICATION_TIME);
}
};
onNotificationTimeEnd = function(){
this.current=null;
this.timeout=null;
if(this.notifications.length>0){
this.notify();
}
};
});
So each time a new notification pops , the view is updated just by adding {{Notification.current}} somewhere in my templateI think React solve parts of the problem while Angular tries to solve the whole problem.
I think there is definetly a middle ground between AngularJS and React virtual DOM that can be found. Let's remember that Misko defines AngularJS as "a better browser",not a framework.
(I'm not a particular fan of JS on the server-side yet..)
Even if I choose react for my view layer, I'm still going to need infrastructure for managing application state. View layer concerns are probably less than 30% of what I get out of Ember. The rest is bidirectional routing between URLs and models, meaningful controller hierarchies, etc.
React is simple because it ignores all that. But any significant app will still need to deal with those things.