5 ms·

I was about to abandon Angular 1 for future projects and go all in on React. And it looked fairly promising, except everything is its own little module. Good fo

I was about to abandon Angular 1 for future projects and go all in on React. And it looked fairly promising, except everything is its own little module. Good for UNIX, but not so good for modules that change so often. Then I started catching up on Angular 2 and TypeScript. It looks like the right mix between new and opinionated. I just don't have time to research a module for data, one for building, one for testing, and one for validation. That's where an opinionated framework comes in handy. I do hope Angular 2 takes off. Any other Angular people out there weighing in between React and Angular 2? If I were a betting man, I say it's going to come down to those two for the next few years.

suhelk 11y ago
I totally agree with you. It took me lots of time just to figure out to write a 'PROPER' react application. There are too many modules to choose from for routing, data acess etc.. Then I tried with Angular 2, it look me less time to get up and running with forms, routing and everything...
- stephenhuey 11y ago
  It may take you even less time with Aurelia!
  - suhelk 11y ago
    Aurelia too seems interesting. Since I have done development in Angular 1.x before, Angular 2.0 was the natural choice. From the look of it, Aurelia seems promising, need to look into more before I need to comment anything.
stephenhuey 11y ago
We've been using Angular on one project and for a new application we were considering using just React with Node or maybe those two with Angular 1 or 2 also. However, after getting started with Aurelia we may stick with it and never consider Angular again!
Matthias247 11y ago
I'm no classical web developer, so I'm not be the best reference, but I used both a little bit for some realtime (mainly websocket driven) webapp for state visualization of remote embedded devices. I started with React, and I'm now on ng2 and happy with it (apart from some hopefully soon fixed bugs). Imho both are ok. What I did not like that much with React was that the virtual DOM did not play nice all the time (strange effects can happen if you place non VDOM aware widgets inside it) and if you not take special care (keys) then reconcilation can produce a messed up representation. These things seem less problematic in ng2. An unexpected very pleasant surprise for me was using the dependency injection mechanism in ng2 - I did not expect it do be useful because I never used something like this before. But now if any sub-sub-subcomponent in my view needs access to a status I don't need to pass it all the way down through unrelated components via props (like in React) but can directly inject it only in the using component. I also had good experiences with MVVM architecture from other projects with other frameworks, so I am happily using this approach also in ng2. For the model component I'm using service objects which are encapsulating the current state, exposing it through observables and are injected into the component (viewmodel) through DI. What I like here is that I can bind the view directly to the observables from the model with the help of async pipes and thereby get an auto-updating behavior with zero boilerplate code. Apart from that there are obviously the major differences - angular has an inbuilt router, React not. But still I wouldn't think of Angular2 as something highly opinionated, you still have lots of flexibility. As I am a big fan of typescript a factor for me was also that ng2 is typescript-first and I don't have to rely on possibly incomplete or 3rd party type definitions. But that might be more of a political factor, the basic typescript support for react is also good (it can even check the types of props in JSX - which currently not possible for ng2 templates) but many 3rd party libraries don't seem to provide type definitions.
d357r0y3r 11y ago
Try Aurelia + TypeScript. I've used Angular 1, Angular 2, and Aurelia, and I think Aurelia is the best choice between those right now. React is fundamentally different, but Aurelia (and its predecessor, Durandal) were always about making component-oriented apps.

suhelk 11y ago

I totally agree with you. It took me lots of time just to figure out to write a 'PROPER' react application. There are too many modules to choose from for routing, data acess etc.. Then I tried with Angular 2, it look me less time to get up and running with forms, routing and everything...

stephenhuey 11y ago
It may take you even less time with Aurelia!
- suhelk 11y ago
  Aurelia too seems interesting. Since I have done development in Angular 1.x before, Angular 2.0 was the natural choice. From the look of it, Aurelia seems promising, need to look into more before I need to comment anything.

stephenhuey 11y ago

We've been using Angular on one project and for a new application we were considering using just React with Node or maybe those two with Angular 1 or 2 also. However, after getting started with Aurelia we may stick with it and never consider Angular again!

Matthias247 11y ago

I'm no classical web developer, so I'm not be the best reference, but I used both a little bit for some realtime (mainly websocket driven) webapp for state visualization of remote embedded devices. I started with React, and I'm now on ng2 and happy with it (apart from some hopefully soon fixed bugs). Imho both are ok. What I did not like that much with React was that the virtual DOM did not play nice all the time (strange effects can happen if you place non VDOM aware widgets inside it) and if you not take special care (keys) then reconcilation can produce a messed up representation. These things seem less problematic in ng2. An unexpected very pleasant surprise for me was using the dependency injection mechanism in ng2 - I did not expect it do be useful because I never used something like this before. But now if any sub-sub-subcomponent in my view needs access to a status I don't need to pass it all the way down through unrelated components via props (like in React) but can directly inject it only in the using component. I also had good experiences with MVVM architecture from other projects with other frameworks, so I am happily using this approach also in ng2. For the model component I'm using service objects which are encapsulating the current state, exposing it through observables and are injected into the component (viewmodel) through DI. What I like here is that I can bind the view directly to the observables from the model with the help of async pipes and thereby get an auto-updating behavior with zero boilerplate code. Apart from that there are obviously the major differences - angular has an inbuilt router, React not. But still I wouldn't think of Angular2 as something highly opinionated, you still have lots of flexibility. As I am a big fan of typescript a factor for me was also that ng2 is typescript-first and I don't have to rely on possibly incomplete or 3rd party type definitions. But that might be more of a political factor, the basic typescript support for react is also good (it can even check the types of props in JSX - which currently not possible for ng2 templates) but many 3rd party libraries don't seem to provide type definitions.

d357r0y3r 11y ago

Try Aurelia + TypeScript. I've used Angular 1, Angular 2, and Aurelia, and I think Aurelia is the best choice between those right now. React is fundamentally different, but Aurelia (and its predecessor, Durandal) were always about making component-oriented apps.