Echo JS 0.11.0

While I agree with @machineghost and @xat, I want to state that I feel a lot of it comes down to incumbents who are more comfortable with other languages/platforms that tend to bring preconceptions in with them.  A lot of web developers have far more experience with PHP, Java or C# than they do JavaScript itself.  They've also attached far more energy into the Angular 1.x ecosystem than anything before it (regarding full JS platforms).

I do think that React will overtake Angular 1, and that Angular2 won't catch a lot of the ng1 users moving forward.  I will make one statement regarding the two... React has some of the most clear, consistent and useful error messages in the console of any web tool that I've ever used as a whole.  ng2 will silently just bork on template errors.  And ng2 isn't much better.

I feel that a more functional approach is better with regards to predictable state and that not following more FP-oriented practices leads to a lot of wierd state issues that tend to be more prevalent when following the ng1 model specifically.  $scope.$apply's existence is the single worst code smell in that ecosystem.  React has evolved to adopt the usage of the broader tooling (cjs modules, babel, etc), while ng1 in particular works against that, and while ng2 is better, there's still a lot of alien parts baked in.

I'm working in ng1.x at my day job currently, and will say there are much bigger issues with organizing JS based projects with the average developer than react vs angular.  On the flip side, I prefer frameworks that lead to code discovery, vs spending half my time in the search tab in my editor looking for the right file to edit.

It is sad to see people spend time criticizing each other, rather than spending time on improving the web technology as a whole. Both Angular 2 and React are good tools, and I am sure we can find good use case for both of them.

Google and Facebook have both invest a lot of money in developing these tools openly, which help drives the web standards. Developers outside of these two companies have also sacrificed their own time contributing to the frameworks, making our life as web developer a lot easier. If anything, all of these open source contributors deserve a lot of respect. If not for their hard work, we would all have to face the set of common problems we used to face some 5 - 10 years ago.

I just want to say "Thank you" to all open source developers. No one forces us to use a framework we don't like, so I suggest we all pick the one that suites you, and show appreciation to those people who has made our life easier.

I think the main problem with this article is that its authors are living in a bubble.  As such, they think they can speak for the popularity of Angular 2, when really the kind of people who will use Angular 2 couldn't care less what they think.

The authors fall in to the subset of all JS programmers who live in the React ecosystem AND are in to stuff like pure functions and Elm.  To be fair, that subset is growing (in part because it has a high density of "thought leaders"), and I think they make a good argument why programmers in the same subset will avoid Angular 2.

But here's what they forget: that subset is a small *minority* of the overall community.  Take the recent (2016) Stack Overflow developer survey.  62,588 Javascript programmers answered it, and here's the popularity breakdown of front-end stacks:

AngularJS, JavaScript, Node.js 16.6%
JavaScript, PHP, WordPress 16.5%
JavaScript, PHP, SQL 14.3%
AngularJS, JavaScript, PHP 11.4%
JavaScript, Node.js, PHP 10.2%
JavaScript, Node.js, React 9.7%
AngularJS, JavaScript, SQL 8.0%

That's right, React users were less than 10% of the total, while Angular users were 36%.

So yeah, the functional-loving subset of the less than 10% of developers who use React will probably eschew Angular 2.  In other news, Linux programmers are unlikely to develop for Windows and it's unlikely to rain on a sunny day.

But does any of this have any relevance on Angular 2's popularity?  I wouldn't bet on it.

I think the many changes to the api / router combined with more general "javascript fatigue" might have caused a lot of folks to hold back on ng2 after getting fingers burned early on. it will be interesting now the RC version nears stability (i hope) to see if the pickup increases.

Imo with the proper tools more enterprise people will gravitate towards A2 - A1 was pretty popular around here, mostly at low and mid enterprise level, while react always had a hipsterish vibe about it.

Angular2 functional programming article https://vsavkin.com/functional-typescript-316f0e003dc6

Putting down Angular 2 while humblebragging about your 10X fp skills in the same breath. Well done.

I think Angular 2 will be mainly used in a smaller enterprise niche. Guess it will be as popular as ExtJS was in 2010.