Well the obvious answer is:
Angular is a complete framework implementing a lot of features and functionality you could need for a full application.
React is only a View-library which means for example it does not have routing concept. ofc there is flux, redux ... and other extra libraries and you can use angular with react ...
The point where you can compare them is ofc the view:
React utilizes the virtual dom and thinks in components, angular 1 does have directives (components) but still uses more of a classic MVC ("MVW") like approach.
If you go for angular 1 it uses a digest loop in the background that will check for changes and rerenders everything -> which means there is no isomorphic render behaviour. Till 1.4 there was only the possibility of 2way bindings -> which means all models where bound to the digest loop cycle -> it can get slow easily.
The next thing is Angular 1 cross scope communications, if not designed clean are a pain in the ass (but this leads to far)
If you go for angular 2 it uses worker to render the views (async / threading) and uses an meta abstraction so isomorphic rendering is possible.
if you go for react, it uses the virtual dom which is a meta abstraction, the rendering can be controlled via the life/update-cycle methods.
j
stuff ;)
Well the obvious answer is: Angular is a complete framework implementing a lot of features and functionality you could need for a full application. React is only a View-library which means for example it does not have routing concept. ofc there is flux, redux ... and other extra libraries and you can use angular with react ...
The point where you can compare them is ofc the view: React utilizes the virtual dom and thinks in components, angular 1 does have directives (components) but still uses more of a classic MVC ("MVW") like approach.
If you go for angular 1 it uses a digest loop in the background that will check for changes and rerenders everything -> which means there is no isomorphic render behaviour. Till 1.4 there was only the possibility of 2way bindings -> which means all models where bound to the digest loop cycle -> it can get slow easily. The next thing is Angular 1 cross scope communications, if not designed clean are a pain in the ass (but this leads to far)
If you go for angular 2 it uses worker to render the views (async / threading) and uses an meta abstraction so isomorphic rendering is possible.
if you go for react, it uses the virtual dom which is a meta abstraction, the rendering can be controlled via the life/update-cycle methods.
ociweb.com/resources/publications/sett/comparison…
you can read this one, in the end like everything it's about taste.... :)