Opinionated Comparison of React, Angular2, and Aurelia

stanislavb wrote: post #2

And we can compare them on LibHunt by CodeQuality, Popularity & Dev Activity React VS Angular https://js.libhunt.com/project/react/vs/angular-js React VS Aurelia https://js.libhunt.com/project/react/vs/aurelia Angular VS Aurelia https://js.libhunt.com/project/angular-js/vs/aurelia BONUS Vue.js VS React https://js.libhunt.com/project/vue/vs/react It seems that Aurelia beats them all by Code Quality...

If you're going to flog your project, you should at least disclaim it as yours; it's only polite.

And you should actually define what "code quality" is, which in this case is apparently a really handwavy claim to cyclomatic complexity and similar metrics (which, while not entirely nonsense, don't mean much, especially at library-code levels when dealing with performance-critical code and the like).

Re: Opinionated Comparison of React, Angular2, and Aurelia

#4

Post by acemarke » Fri, Apr 07, 2017, 6:34 AM UTC

stanislavb wrote: post #2

And we can compare them on LibHunt by CodeQuality, Popularity & Dev Activity React VS Angular https://js.libhunt.com/project/react/vs/angular-js React VS Aurelia https://js.libhunt.com/project/react/vs/aurelia Angular VS Aurelia https://js.libhunt.com/project/angular-js/vs/aurelia BONUS Vue.js VS React https://js.libhunt.com/project/vue/vs/react It seems that Aurelia beats them all by Code Quality...

Rather depends on how they're measuring "code quality". A very brief search didn't turn up any specific description of their metric.

If it's simply, say, "number of issues", or even something like "average age of open issues", then an actively used lib like Angular or React is likely to have "less quality" simply because more people have been using it and filing issues over time.

Re: Opinionated Comparison of React, Angular2, and Aurelia

#5

Post by fraserharris » Fri, Apr 07, 2017, 6:35 AM UTC

My key to success with react-router was to use context and redux to get props to the routed components. Sub-components from there can accept props directly. After a while it feels natural - any necessary information is stored in the store.

Re: Opinionated Comparison of React, Angular2, and Aurelia

#6

Post by fraserharris » Fri, Apr 07, 2017, 6:35 AM UTC

My key to success with react-router was to use context and redux to get props to the routed components. Sub-components from there can accept props directly. After a while it feels natural - any necessary information is stored in the store.

Re: Opinionated Comparison of React, Angular2, and Aurelia

#7

Post by Matthias247 » Fri, Apr 07, 2017, 6:37 AM UTC

Regarding the Angular DI part: You don't need "provides" anymore on each component, afaik it's even deprecated. You just need to define it once on the module that defines the DI providers. And in the module of the component import that module. But your findings may already have been from some time ago where things were different in Angular land. That's for me the saddest story of Angular 2: Between alpha, beta, RC and final release dozens of things changed, which required me to constantly change my app. Now that it's stable I'm quite sophisticated with it.

Re: Opinionated Comparison of React, Angular2, and Aurelia

#8

Post by tribby » Fri, Apr 07, 2017, 6:42 AM UTC

acemarke wrote: post #4

stanislavb wrote: post #2

And we can compare them on LibHunt by CodeQuality, Popularity & Dev Activity React VS Angular https://js.libhunt.com/project/react/vs/angular-js React VS Aurelia https://js.libhunt.com/project/react/vs/aurelia Angular VS Aurelia https://js.libhunt.com/project/angular-js/vs/aurelia BONUS Vue.js VS React https://js.libhunt.com/project/vue/vs/react It seems that Aurelia beats them all by Code Quality...

Rather depends on how they're measuring "code quality". A very brief search didn't turn up any specific description of their metric. If it's simply, say, "number of issues", or even something like "average age of open issues", then an actively used lib like Angular or React is likely to have "less quality" simply because more people have been using it and filing issues over time.

lumnify describes the criteria[1] but is incredibly vague about it. unless/until they give detailed reports on each project explaining how they arrived at their conclusions I think it's fair to treat these grades as pulled out of thin air. and even then it would be of very little/probably still no value. every project is different and you need to evaluate your tooling based on the situation.

1. https://lumnify.com/grades/

Re: Opinionated Comparison of React, Angular2, and Aurelia

#9

Post by Kiro » Fri, Apr 07, 2017, 6:43 AM UTC

I would love to hear how people solve the snackbar problem in React. I don't even see how you would solve it with redux since that's just the state.

Re: Opinionated Comparison of React, Angular2, and Aurelia

#10

Post by stanislavb » Fri, Apr 07, 2017, 6:44 AM UTC

acemarke wrote: post #4

stanislavb wrote: post #2

And we can compare them on LibHunt by CodeQuality, Popularity & Dev Activity React VS Angular https://js.libhunt.com/project/react/vs/angular-js React VS Aurelia https://js.libhunt.com/project/react/vs/aurelia Angular VS Aurelia https://js.libhunt.com/project/angular-js/vs/aurelia BONUS Vue.js VS React https://js.libhunt.com/project/vue/vs/react It seems that Aurelia beats them all by Code Quality...

Rather depends on how they're measuring "code quality". A very brief search didn't turn up any specific description of their metric. If it's simply, say, "number of issues", or even something like "average age of open issues", then an actively used lib like Angular or React is likely to have "less quality" simply because more people have been using it and filing issues over time.

Hey, thanks for the interest. It's much more complex. There's a link at the bottom of the pages pointing to a basic explanation - https://lumnify.com/grades/ . I hope that helps.