Dimitris Klisiaris’s answer to Why would I use React over AngularJS?

  • But if Library A and B both try and do X, they can compete in a direct fashion in discrete and measurable ways.
  • By using small libraries – components with a dedicated purpose and a small surface area – it becomes possible to pick and mix , to swap parts of our front end stack out if and when they are superceded
  • You can move your legacy projects to new technologies incrementally , rather than rewriting everything, providing you stick to good practices and wrap those libraries carefully.
  • If you find you don’t like the templating language or error handling, you don’t have to rethink the entire project, you just hot-swap the component for another and you’re on your way again.
  • Small components usually do one thing very well .


@webdif: Why would I use React over AngularJS? Componentization! #JS

This page may be out of date. Save your draft before refreshing this page. Submit any pending changes before refreshing this page.

I think what you asking here is why would i use smaller components like the view-only library react (probably with some event module like flux) over a full-fledged MVC framework like angular?.

Small components usually do one thing very well.

There will never be a perfect framework so you can just hack the most relevant features together using npm.

Small libraries have simple documentation and they are easy to set up and use.

Any problems and there’s no waiting for the next release of the entire framework, you simply throw up an issue, the authors fix it, push it and then bam it’s on npm for everyone else and no other components have been disturbed.

If you find you don’t like the templating language or error handling, you don’t have to rethink the entire project, you just hot-swap the component for another and you’re on your way again.

By using small libraries – components with a dedicated purpose and a small surface area – it becomes possible to pick and mix, to swap parts of our front end stack out if and when they are superceded

New projects can replace only the parts that matter, whilst core functionality whose designs are settled – routing APIs, say – can stay exactly the same between the years.

You can move your legacy projects to new technologies incrementally, rather than rewriting everything, providing you stick to good practices and wrap those libraries carefully.

When different problems are answered by different libraries, their solutions can compete directly. If Framework A does X well and Y badly, compared to Framework B’s great Y and shaky X, you’re stuck. But if Library A and B both try and do X, they can compete in a direct fashion in discrete and measurable ways.

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Dimitris Klisiaris’s answer to Why would I use React over AngularJS?

You might also like More from author

Comments are closed, but trackbacks and pingbacks are open.