Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Opinionated Comparison of React, Angular2, and Aurelia

github.com

Post reply on HN
Print view View original

11–20 of 169 posts

Re: Opinionated Comparison of React, Angular2, and Aurelia

#11

Post by stanislavb »

tribby wrote: post #8
acemarke wrote: post #4

Earlier quoted context omitted.

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/gr…

They are not pulled out of thin air. You should contact them, and they will come with an answer. The algorithms have been tuned based on feedback from a number of Start Ups in Sydney.

Re: Opinionated Comparison of React, Angular2, and Aurelia

#12

Post by searchhn »

> There are a few more frameworks I would have loved to try, including Polymer and Vue.js. There just wasn't enough time to do a deep dive with all of them.

I hope he gives Vuejs a try. As a javascript beginner, who tried Angular, Angular2, A bit of React and VueJS, I just loved the flexibility and approach of VueJS. I was instantly productive thanks to the amazing documentation and vue-cli that just worked out of the box setting up my project.

PS: Never really spent much time on React as I tried it after VueJS and did not feel like proceeding much further with my tests.

Re: Opinionated Comparison of React, Angular2, and Aurelia

#13

Post by tribby »

stanislavb wrote: post #11
tribby wrote: post #8

Earlier quoted context omitted.

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/gr…

They are not pulled out of thin air. You should contact them, and they will come with an answer. The algorithms have been tuned based on feedback from a number of Start Ups in Sydney.

they can open-source their methods/algorithms for public review if they want anyone to take their scores seriously.

Re: Opinionated Comparison of React, Angular2, and Aurelia

#14

Post by SebastianM »

Comparing plain React with Angular and Aurelia is completely useless. You cannot write a big serious application with Form Validation, Data Fetching, Testing, etc, just with React itself. A fair comparison would be to write a whole "real world" project and then see what parts you have to use and learn to be able to write a full React application.

Re: Opinionated Comparison of React, Angular2, and Aurelia

#16

Post by Sacho »

Kiro wrote: post #9

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.

The snackbar problem is actually what redux is built to solve. You would "provide the toast()" function by having components dispatch a "toast" action. From there, your reducer would modify the snackbar state accordingly, e.g. by implementing a stack of toasts, and you would have a single global component render that state into popups.

Re: Opinionated Comparison of React, Angular2, and Aurelia

#17

Post by SebastianM »

> Angular's routing seems to involve "one big routing config".

That's wrong. You can split the routing configuration just like in react-router or Aurelia. It also supports lazy loading of child routes and components. So you don't have one giant application to serve at bootup time. It is also documented really well: https://angular.io/docs/ts/latest/guide/ngmodule.html#!#lazy...

Re: Opinionated Comparison of React, Angular2, and Aurelia

#18

Post by SebastianM »

Matthias247 wrote: post #7

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 an…

> afaik it's even deprecated.

No, it's not. You use providers on a component when you want to have a new instance of that Service when a new Component instance of that type gets created. So you have complete control over the DI. More details here: https://angular.io/docs/ts/latest/guide/dependency-injection...

Re: Opinionated Comparison of React, Angular2, and Aurelia

#19

Post by platz »

> Save the global components off as global variables and just use them ... When my ActivityIndicator component mounts, it saves itself off to a global. Any code can import busy and run busy.start() and busy.stop().

What is the story that FP folks need to tell here, so that people don't do things like this?

Post reply on HN