3 ms·
I'm currently in the same boat. Both are similar in that they are component-oriented. There are two important factors in my mind. 1. The ecosystem (as you me
by asher_ 10y ago
I'm currently in the same boat.
Both are similar in that they are component-oriented.
There are two important factors in my mind.
1. The ecosystem (as you mentioned). React has a clear head start here, but I expect Angular2 to make some gains over time.
2. Angular2 gives you a full framework, and as they say now, a whole platform. React is smaller and you rely on a bunch of other packages to get all the extra features you need. If you want a full solution, Angular2 gives you that.
This can be argued as a good thing or a bad thing. More flexibility with React, but also more things you need to figure out and make a decision about. With Angular2, once you buy in, you don't need to make all of those decisions.
In my particular circumstance, which is to migrate an Angular1 app to a newer framework over time (mainly for the server side rendering features), Angular2 provides a clearer path and offers some nifty features like component styles that allow a similar migration with CSS.
- BigJono 10y agoAs someone who has never used Angular but is interested in Angular 2, can you give some examples of the framework-y things it provides that React doesn't? Redux is really the only thing I find necessary for what I've developed so far, and I'm sure Angular has it's equivalent, but what else does it have?
- Bahamut 10y agoIt gives the ability to do validation with form components, using a nice XHR abstraction, and a router - all optional. It also provides a robust DI framework and set of testing tools.
- gldalmaso 10y ago>> Angular2 gives you a full framework, and as they say now, a whole platform. So did Angular 1, and then they threw it under a bus. Now developers have to either refactor for a whole new framework or get stuck with a legacy one. Javascript ecosystem is becoming so hostile a project deprecates itself in favor of a clean rewrite and the migration path is an afterthought. Will think twice before adopting google frameworks and tools. Javascript ecosystem is in dire need of stability and trust.
- popmystack 10y ago>and then they threw it under a bus. They didn't just do this "because." There were sound technical reasons to do so. Angular made the correct decision, in my opinion, and decided to cut its losses immediately and right the wrongs within the framework.
- boubiyeah 10y agoWell... I would argue that angular 2 is not even better than angular 1 so it will probably happen again :p It's more performant, but that's about it. It's insane, java/spring like complex for no reason.
- popmystack 10y agoReally? So mobile support, change detection revamp, TypeScript, the removal of $scope, and all the routing changes are all just "meh" to you?
- Roboprog 10y agoWellllllll... I does make me want to learn React & React Mobile if I have to largely start over, anyway. Not saying ng-2 is not an improvement, just that it's a big change to take in.