The reality is that you should know Angular AND you should know React. These are not mutually exclusive.
I'm very pragmatic about frameworks. Yes, React might be technically better than Angular 2, but it has to be better at putting food on the table. It probably will be.
In the meantime, there are a lot of Angular 1 projects that will need migrating to Ang 2.
React as a term is understandably a bit polluted though.
Do you have a citation for that? I still see tons of user land projects using angular 1.
I think there are probably still more Angular devs, but I'll be interested to see how it evolves in the next few years.
And I'm sure you did fine work, but small business print shops are not exactly industry trend setters. What difference would it make in the bigger picture if you had chosen Handlebar for that project?
Sometimes you have questions on StackOverflow that compare eg Angular with React, and they usually raise a lot of good points, but they are missing several dimensions:
* the products evolve, but the SO answers often don't
* the trends change as well, so what was seen as best practice 1yr ago may not be well regarded now
* you do not have an objective representation of how many people are actually supporting each technology
I think there's definitely something to be done in that space.
I personally use React and Node.js for a lot of the stuff I work on these days (both professionally and freelance projects). I know a lot of developers who use React, so while a Google search (not exactly scientific either in my opinion) yields low use of React, just based on the circle that I frequent, there are a lot of people using React and in 2016 we will see more people using it. The last two freelance projects I worked on (for pretty large companies) were built using React, word is travelling fast.
A lot of people are using Angular 1.x, but I know for a fact that not all of them will migrate over to 2.0 when the time comes. The learning curve might be smaller, but Angular 2 still falls into the trap of being over engineered in certain parts (like template syntax).
Unfortunately, bower does not seem to collect download stats (I assume because downloads don't go through a Bower-controlled server), and I find it very likely that react usage is strongly correlated with NPM usage. React treats bower very much as a second-class citizen, even using a separate repo for its bower repository.
I say that as someone who thinks React is the future of JavaScript development and there's no chance I will ever go back to separate templates so Angular of whatever version is just automatically disqualified. It would be like going back in time and I do not want to do this.
It works really well. Including breakpoints in chrome,etc.
I really hope that React makes this more public - it makes it for quick and dirty prototyping. P.S. love ES6. Performance be damned!!
Both are meant for engineers, if by that you mean developers.
http://www.ryan-williams.net/hacker-news-hiring-trends/2015/...
I think, to a large extent, it depends on people's reaction to the word "framework".
Disclaimer: we switched to React at my company.
But checking from HN, blog postings, job announcements, team posts, new turorials (video, books), etc, React seems to be winning now.
https://www.google.com/trends/explore#q=reactjs%2C%20angular...
Obviously the Google trend search for "react" has lots of false positives, but some of the major news points it picked out include references to the right react.
Totally not inspired by Elm and traditional FRP. I mean, I use it daily and it's great, but you have to realize that a lot of what React brings to the front is bundling some well-known paradigms together.
No, it hasn't
> simplistic component based approach.
"Simplistic"
> Unlike React, Google does not really treat Angular as a first-class citizen because they have such split focus and conflicting React like library for web components called Polymer. They provide some resources, but nowhere near the amount of resources that Facebook throws behind React and React Native.
Facebook does one thing. Google does many things.
React has recently dominated headlines and in another few months, something else will. Meanwhile, people will keep using stuff from 3 years ago.
For example, OkCupid (from what I've heard) based its mobile architecture on AngularJS, but then once React matured, they basically declared all their Angular legacy and promptly shifted to doing everything in React.
Even https://www.madewithangular.com/ doesn't make clear how AngularJS is being used in the few websites it showcases. Lyft uses it for its homepage, but it does not use it anywhere else. Likewise, one the homepage for healthcare.gov, one of the websites provided: does it use a lick of "ng-" anything in its HTML.
I don't disagree that Angular solves an additional set of problems, but I think the hype behind React is real, i.e. it's an actually good framework. Also, being an AngularJS developer myself, I too really dislike feeling that I've wasted my time learning yet another piece of tech that will be outmoded in the next year or so.
Personally i love Typescript as well and i am pretty sure NG2 will get a lot of thrust behind it, now that the api is stable.
Unlike React, Google does not really treat Angular as a first-class citizen because they have such split focus and conflicting React like library for web components called Polymer. They provide some resources, but nowhere near the amount of resources that Facebook throws behind React and React Native.
Now lets talk about the fact that the Angular 2 project got off to a shaky start and I know they actually rewrote various parts from scratch more than once (hence why it took so long to reach beta, approximately 2 years). That horrible templating syntax needs to be mentioned, the decision to use square and rounded brackets for binding events/data and using things like asterisks in my opinion makes Angular 2 fall into the same trap that Angular 1 did in regards to developer accessibility.
I am really loving TypeScript these days and I think the decision to support it as a first-class citizen out-of-the-box was a good one (the partnership with Microsoft definitely paid off). But with that said, I think Rob Eisenberg (of Durandal fame) beat the Angular 2 team to the punch in the small space of a year in releasing his framework Aurelia (http://aurelia.io). It is what Angular 2 should have been in my opinion. Nice syntax, convention over configuration and a breeze to use.