Live data from Hacker News

Angular vs. React vs. Vue

medium.com

71–77 of 77 posts

Re: Angular vs. React vs. Vue

#71
post #2

Ember is so good, it does not need comparisons any more :) https://medium.com/@alvincrespo/ember-your-best-bet-b5cd7275...

Ember seems to have half as many downloads as Vue nowadays

Interactive histogram of daily downloads:

https://npmcharts.com/compare/react,angular,@angular/core,em...

Re: Angular vs. React vs. Vue

#72

Earlier quoted context omitted.

Preact https://preactjs.com/ is a good purely MIT licensed drop in replacement for React if licensing is an issue

It claims to be a drop in replacement, but it isn't.

Can you expand on this at all? I've looked at it as a replacement and I understand there are things like prop-types that are missing, but my understanding is that there are other libraries you can can use in addition to preact that give you 100% compatibility.

Re: Angular vs. React vs. Vue

#73
post #13
post #10

Earlier quoted context omitted.

I think angular just makes more sense in larger projects. Imo, It has quite a lot of overheard that only pays off when working in larger teams.

> I think angular just makes more sense in larger projects. I remember people saying exactly that with Extjs back in the days, with no proof whatsoever. Can you explain how angular makes more sense in larger projects? > that only pays off when working in larger teams. what makes it better for "large teams" ?

It always felt to me that the purpose of Angular was to give a 'large team using Java' type workflow to development, with the idea being that doing it this way you can just slot in a new angular developer when the previous one goes crazy and runs out the building screaming. But I've only worked on one Angular project, so this is a feeling on my part, not a well worked out theory of how it actually is.

Re: Angular vs. React vs. Vue

#74
Instead of comparing GitHub stars, better check npm trends: https://npmcharts.com/compare/react,angular,@angular/core,vu...

AngularJS, Angular 2+, Vue.js... all have a somewhat similar approach. React is more of a newer paradigm, it fixes most of the problems older stacks had in a radically different way, yet elegant. This article fails to explain the different paradigms.

Also please stop "Want to use TypeScript? Go with Angular!". React and its ecosystem has the best TypeScript experience thanks to JSX. JSX being just JavaScript, everything is checked by TypeScript like any regular JavaScript piece of code. You cannot do that with HTML templates.

Re: Angular vs. React vs. Vue

#75

I'm just really glad Vue is now included in every "X vs Y" framework, or "choosing a js framework", almost every article for the past two years have only been for Angular or React.

I think Vue is great but I wish Aurelia would show up in more of these comparisons as well: http://aurelia.io

I thought about including it but had to stop somewhere. Aurelia really looks promising!

Re: Angular vs. React vs. Vue

#76
post #2

Ember is so good, it does not need comparisons any more :) https://medium.com/@alvincrespo/ember-your-best-bet-b5cd7275...

One of the big reasons I avoid Ember is exactly this attitude. I have worked with people who, in a complete serious manner, think that Ember is so much better than everything else for everything. They won't STFU about it. It reminds me a lot of Rails bootcamp graduates.

Pretty interesting. I would have agreed with you a couple years ago. And I wanted to do a follow up on what I think was the most damaging issue with Ember back in 2012-2013. But you're hitting on a common topic I've heard quite frequently.

More than happy to hear more about it and get your general thoughts on the subject. Feel free to reach out.

Re: Angular vs. React vs. Vue

#77
post #44

Earlier quoted context omitted.

I think Vue is great but I wish Aurelia would show up in more of these comparisons as well: http://aurelia.io

You have a number of comments that advertise this but never offer any reason alongside it.

I've been building for the web for 15 years, and Aurelia feels more natural to me. Granted, my Angular projects were all in Angular 1 and it has since undergone a massive rewrite, almost as if it's a different framework now. But based on my extensive experience with web applications using Java, Ruby and Node.js on the servers (sometimes Single Page Application frontends, sometimes minimals JS with jQuery libraries, etc), Aurelia just felt more naturally web-like. That doesn't mean Angular is not able to do the job, but it feels more like using a heavier tool that doesn't belong.

Aurelia also feels easier to build with (less unnecessary boilerplate) and more maintainable in the end. The community is small but has made immense strides in a short amount of time. There is a company backing it, but a very small one, not a giant one such as Google or Facebook (and those giant ones make no guarantees, but the small one backing Aurelia has emphasized their long-term commitment time and time again). They have an ever-increasing number of community contributors and features have been added at a rapid pace. Since I began a year and a half ago, UI toolkits have regularly added Aurelia integrations. The CLI has improved by leaps and bounds.

You can find out more on their website and other blogs and articles around the web, but you may find this helpful:

https://stackoverflow.com/questions/41853743/angular-2-vs-au...

Post reply on HN