Opinionated Comparison of React, Angular2, and Aurelia • Hacker News Board

Re: Opinionated Comparison of React, Angular2, and Aurelia

#61

Post by 8note » Fri, Apr 07, 2017, 9:30 AM UTC

mistermumble wrote: post #41

mememaestro wrote: post #34

Earlier quoted context omitted.

What is the snackbar problem?

See the section in the article with the heading "Dependency Injection". It talks about a specific scenario where there is one component that needs to show the state of the entire system (an activity light turned on, for example), where any component can trigger this, but the last component to become inactive turns the light off.

isn't that Facebook's example for why they made react? the light is the number of notifications/chat messages you have available,and they could never get it to stay consistent?

Re: Opinionated Comparison of React, Angular2, and Aurelia

#62

Post by ferto » Fri, Apr 07, 2017, 9:34 AM UTC

I know yet another Framework but a lot of your issues I think are solved with Vuejs as they provide a quite mature and well documented component library which is using Streams (under the hood) and their single-file approach solves a lot of issues (https://vuejs.org/v2/guide/single-file-components.html).

additionally, they provide their own router, redux implementation which are all working very well with the components.

I think Vuejs has some great approaches which makes it easy especially for people who want to use new frontend stuff but not with the complexity and technical depth Angular2, React and others introduce.

Re: Opinionated Comparison of React, Angular2, and Aurelia

#63

Post by cjCamel » Fri, Apr 07, 2017, 9:35 AM UTC

Aurelia is componentised, so you can use React as the view engine which (in theory) would give you the benefits of React alongside decent routing and DI (which can also be swapped out).

One other thing that Aurelia is good about is not requiring a lot of DSL. The maintainers aren't interested in developer lock in or mindshare like Facebook and Google, so the code you write is more portable than with React or Angular - it's a shame the author didn't make more of this.

Additionally the maintainers provide guarantees that they won't pull the projects, which Facebook and Google do not.

That said, it's hard to argue that the ecosystem around React+Redux and Angular makes it very hard for the smaller players to get a look in for all sorts of reasons.

Re: Opinionated Comparison of React, Angular2, and Aurelia

#64

Post by voidr » Fri, Apr 07, 2017, 9:35 AM UTC

stymaar wrote: post #40

> And the React ecosystem tends to either lack typings or provide poor/broken typings. React integrates really well with flow[1] (which is not surprising because they're both developed at Facebook) and in my experience flow's typesystem is more powerful (OCaml inspired) than TypeScript one (C# inspired): - non-nullable types by default is a big deal (they added support for non-nullable types in TypeScript 2, but enab…

> React integrates really well with flow[1] (which is not surprising because they're both developed at Facebook)

It can integrate just as well with TypeScript.

> flow's typesystem is more powerful (OCaml inspired)

It lacks access control for class properties/methods, I wouldn't call that powerful. https://flow.org/en/docs/types/classes/

Re: Opinionated Comparison of React, Angular2, and Aurelia

#65

Post by beachy » Fri, Apr 07, 2017, 9:36 AM UTC

Swizec wrote: post #48

daliwali wrote: post #42

The ending is what makes this article: >Overall, I'm not 100% sure I made the right choice, but I only have to live with it for two years. People are great at short term thinking, and tend to be terrible at long term thinking. Just some anecdata: I had a look at some source code for a 10+ year old web app before JS libraries were popular. I could understand perfectly how a click on a link resulted in a URL hash chang…

> Web apps today just get rewritten every two years. Your startup either dies or lives long enough to become a hodgepodge of ten different frameworks.

Harsh but so true.

Re: Opinionated Comparison of React, Angular2, and Aurelia

#66

Post by wereHamster » Fri, Apr 07, 2017, 9:39 AM UTC

stymaar wrote: post #40

> And the React ecosystem tends to either lack typings or provide poor/broken typings. React integrates really well with flow[1] (which is not surprising because they're both developed at Facebook) and in my experience flow's typesystem is more powerful (OCaml inspired) than TypeScript one (C# inspired): - non-nullable types by default is a big deal (they added support for non-nullable types in TypeScript 2, but enab…

> React integrates really well with flow

No. The flow types around React are really poor. There are many things flow can't represent. The types are 'private' (all types in flow with a dollar in the name are private, not publicly supported. eg. React$Element).

The implementation of React$Element is hardwired into flow. If you have to include specific support for libraries it tells a lot about the expressiveness of the underlying type system, doesn't it?

There is no way to represent a react node, fragment etc. Properly typing children of a react component is impossible.

Re: Opinionated Comparison of React, Angular2, and Aurelia

#67

Post by BigJono » Fri, Apr 07, 2017, 9:48 AM UTC

SebastianM wrote: post #14

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.

This is just blatantly false. I've got several apps in production using nothing but React, React-Router and a unit testing library. In-fact I'd posit that it's easier to write good, maintainable code using a minimal toolset than it is to cram a bunch of rubbish in there that dictates your software's architecture. I've seen more people shoot themselves in the foot with things redux and redux-thunk than I have seen use them properly.

Re: Opinionated Comparison of React, Angular2, and Aurelia

#68

Post by severila » Fri, Apr 07, 2017, 9:50 AM UTC

WA wrote: post #29

I've spend a lot of time evaluating Angular + Ionic, Vue and React. My goal is to rewrite my webapp as a SPA with complimentary mobile apps. Maximum code sharing would be nice. I'd like to add to the discussion what I learned and also add Vue for comparison. Vue felt less intimidating at first, whereas React seemed to be overly complicated. Truth is, both are actually quite similar. The problem is that every single t…

  "The main advantage of React over Vue and Angular is: React Native. Vue doesn't have anything close to it."

Have you tried Quasar? (http://quasar-framework.org/) We're using it right now for a customer project and I'm very happy so far. Performance feels better than Ionic2.

Re: Opinionated Comparison of React, Angular2, and Aurelia

#69

Post by bshimmin » Fri, Apr 07, 2017, 9:50 AM UTC

renesd wrote: post #57

searchhn wrote: post #12

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

The vue looks good. Yeah, Vue.js is for people who make things. React is for enterprises who don't seem to mind being 3 months late shipping basic stuff. In react everything is done in the template language. It's a sort of reverse template language, that doesn't even really use proper html for things. So weird. Vue is just all together, and is based on web standards. Not a weird thing by facebook enterprise developer…

Ah, so jQuery spaghetti has now been replaced by React messes. I can also contribute that I've seen some Angular abominations and - a year or two back - some baleful Backbone projects. It's almost like whatever the framework or the library you give developers to use, regardless of its quality or scope, they're capable of making a mess with it! Hard to imagine, I know.

Re: Opinionated Comparison of React, Angular2, and Aurelia

#70

Post by boubiyeah » Fri, Apr 07, 2017, 9:53 AM UTC

bshimmin wrote: post #69

renesd wrote: post #57

Earlier quoted context omitted.

The vue looks good. Yeah, Vue.js is for people who make things. React is for enterprises who don't seem to mind being 3 months late shipping basic stuff. In react everything is done in the template language. It's a sort of reverse template language, that doesn't even really use proper html for things. So weird. Vue is just all together, and is based on web standards. Not a weird thing by facebook enterprise developer…

Ah, so jQuery spaghetti has now been replaced by React messes. I can also contribute that I've seen some Angular abominations and - a year or two back - some baleful Backbone projects. It's almost like whatever the framework or the library you give developers to use, regardless of its quality or scope, they're capable of making a mess with it! Hard to imagine, I know.

And likewise, you can/could do some excellent coding with 0 framework :D