3 ms·

This kind of comparison is meaningless. Compare React to Veu.js, as these are both view renderers, not full MV* frameworks. And compare Angular2 to Ember (with

This kind of comparison is meaningless. Compare React to Veu.js, as these are both view renderers, not full MV* frameworks. And compare Angular2 to Ember (with Fastboot), both of which are opinionated MV* frameworks. Not sure why this is on the front page

platz 10y ago
You make it sound like no one has ever had to make a decision to choose between different frameworks.
pluma 10y ago
Because when people say "React" they don't mean "React" but "React plus X" (React Router, Redux, what have you). Or the "React ecosystem". In the real world "Angular" (i.e. the Angular ecosystem), "Ember" (i.e. the Ember ecosystem), "React" (i.e. the React ecosystem), "Aurelia" (i.e. pretty much just Aurelia because nobody actually uses Aurelia so there's no ecosystem -- just kidding, maybe) etc compete against each other. It's not about the actual libraries themselves. One could toss in "Backbone" (i.e. jQuery plus Backbone) for good measure but barely anyone considers Backbone a viable option for new code (rather than something you want to migrate old code away from). It's on the front page because people who aren't already dedicated to any of these ecosystems literally ask "should I use React or Angular (or Ember or ...)?". I think the only mistake is to talk about "frameworks" as if the choice is a choice between frameworks when it's obviously about the ecosystems not libraries (whether those libraries are frameworks or not).
awjr 10y ago
I found it interesting and he specifically pulled in react-router to get the balance needed for the comparison to be valid.
- SebastianM 10y ago
  When your application is just some views plus some routing - then that would be a fair comparison. But in most real world situations (SPA) it's much more: Form validation, Data Fetching, Unit Testing, Component styling, Translations, Modularization, ...
  - pluma 10y ago
    Obviously therefore nobody writes real world SPAs with React. /s
  - BigJono 10y ago
    All of which is easily done using plain old Javascript (with the exception of unit testing).
camus2 10y ago
> not full MV* frameworks Vue.js has an official router, and an official "redux" like data store. https://router.vuejs.org/en/ https://router.vuejs.org/en/ https://vuex.vuejs.org/en/intro.html https://vuex.vuejs.org/en/intro.html It is absolutely a full MV* framework. Vue.js also supports server-side rendering, in fact I use Vue.js as my template engine when using node.js . https://vuejs.org/v2/guide/ssr.html https://vuejs.org/v2/guide/ssr.html Angular2 router is in a separate package, does it make is short of a full MV* solution? no. What I like with Vue.js is that complexity is opt-in. In the sense that it doesn't force you to use a cli (it has a cli), it doesn't force you to use webpack or an asset pipeline (it has support for webpack). It doesn't force you to use a third party language, but you can... You start small then scale with your needs, instead of having to deal with complexity upfront. That used to kind of be the case with AngularJS 1 too, that's why it got widely adopted.

platz 10y ago

You make it sound like no one has ever had to make a decision to choose between different frameworks.

pluma 10y ago

Because when people say "React" they don't mean "React" but "React plus X" (React Router, Redux, what have you). Or the "React ecosystem". In the real world "Angular" (i.e. the Angular ecosystem), "Ember" (i.e. the Ember ecosystem), "React" (i.e. the React ecosystem), "Aurelia" (i.e. pretty much just Aurelia because nobody actually uses Aurelia so there's no ecosystem -- just kidding, maybe) etc compete against each other. It's not about the actual libraries themselves. One could toss in "Backbone" (i.e. jQuery plus Backbone) for good measure but barely anyone considers Backbone a viable option for new code (rather than something you want to migrate old code away from). It's on the front page because people who aren't already dedicated to any of these ecosystems literally ask "should I use React or Angular (or Ember or ...)?". I think the only mistake is to talk about "frameworks" as if the choice is a choice between frameworks when it's obviously about the ecosystems not libraries (whether those libraries are frameworks or not).

awjr 10y ago

I found it interesting and he specifically pulled in react-router to get the balance needed for the comparison to be valid.

SebastianM 10y ago
When your application is just some views plus some routing - then that would be a fair comparison. But in most real world situations (SPA) it's much more: Form validation, Data Fetching, Unit Testing, Component styling, Translations, Modularization, ...
- pluma 10y ago
  Obviously therefore nobody writes real world SPAs with React. /s
- BigJono 10y ago
  All of which is easily done using plain old Javascript (with the exception of unit testing).

camus2 10y ago

> not full MV* frameworks Vue.js has an official router, and an official "redux" like data store. https://router.vuejs.org/en/ https://router.vuejs.org/en/ https://vuex.vuejs.org/en/intro.html https://vuex.vuejs.org/en/intro.html It is absolutely a full MV* framework. Vue.js also supports server-side rendering, in fact I use Vue.js as my template engine when using node.js . https://vuejs.org/v2/guide/ssr.html https://vuejs.org/v2/guide/ssr.html Angular2 router is in a separate package, does it make is short of a full MV* solution? no. What I like with Vue.js is that complexity is opt-in. In the sense that it doesn't force you to use a cli (it has a cli), it doesn't force you to use webpack or an asset pipeline (it has support for webpack). It doesn't force you to use a third party language, but you can... You start small then scale with your needs, instead of having to deal with complexity upfront. That used to kind of be the case with AngularJS 1 too, that's why it got widely adopted.