The State of JS Survey 2018 - the Angular Scoop
Tags: javascript, angular
Published: 2018-11-21 09:05:59

---
title: The State of JS Survey 2018 - the Angular Scoop
published: true
tags: javascript, angular
canonical_url: https://www.telerik.com/blogs/the-state-of-js-survey-2018-the-angular-scoop
---

As you sit down to Thanksgiving or Friendsgiving dinner this week(if you’re into that sort of thing), you might be interested to know the results of the annual [State of JS Survey for 2018](%E2%80%9Dhttps://2018.stateofjs.com/%22). We know this week should mostly be about spending time with loved ones and taking time away from code, so we’ll keep this update short and sweet. We'll cover a lot of ground but focus primarily on Angular.

![bitmoji of me waving in falling leaves saying ‘happy thanksgiving’](https://www.telerik.com/sfimages/default-source/blogs/2018/2018-11/state-of-js-2018/img-1.png?sfvrsn=667ac0d7_2)

## Popularity of Frameworks in 2018

[![screenshot of overall results for front-end frameworks in 2018](https://www.telerik.com/sfimages/default-source/blogs/2018/2018-11/state-of-js-2018/img-2935c0ad7711045c4a0656cd28863b0ac.jpg?sfvrsn=d9876f18_2)](https://www.telerik.com/sfimages/default-source/blogs/2018/2018-11/state-of-js-2018/img-2935c0ad7711045c4a0656cd28863b0ac.jpg?sfvrsn=d9876f18_2)

The overall results for popularity show React, Vue.js, and Angular in the lead, followed by Preact, Ember, and Polymer. If we focus just on “Used it and would use it again” category, we can see the percentages break down which puts these three frameworks firmly in the lead. I was surprised that Preact made the list of top four, so I checked out exactly _what_ frameworks were in the survey and found this lovely list:

[![screenshot of all the frameworks mentioned in the JS survey for 2018](https://www.telerik.com/sfimages/default-source/blogs/2018/2018-11/state-of-js-2018/img-2.png?sfvrsn=229ba64b_2)](https://www.telerik.com/sfimages/default-source/blogs/2018/2018-11/state-of-js-2018/img-2.png?sfvrsn=229ba64b_2)

Some of the other top frameworks that didn’t make top 6, included Svelte, Aurelia, Hyperapp, and Backbone. All received under 200 mentions.

Now might be an excellent time to remind everyone:

> These results are only as good as the audience they surveyed and may not accurately represent the dev community as a whole.

So while it can be fun to look at the results and hypothesize the _why_ behind them, every result should be taken with a grain of salt.

![bitmoji of me in a salt shaker](https://www.telerik.com/sfimages/default-source/blogs/2018/2018-11/state-of-js-2018/img-4.png?sfvrsn=10410380_2)

## Salary for Devs of Frontend Frameworks in 2018

I think it’s remarkable, if you check out the salary for these same frameworks, the chart is almost exactly inverse from the popularity chart — Ember, Polymer, and Preact leading for highest Salaries overall and on average.

[![screenshot of salary breakdown between front-end framework jobs](https://www.telerik.com/sfimages/default-source/blogs/2018/2018-11/state-of-js-2018/img-5.png?sfvrsn=5e92d879_2)](https://www.telerik.com/sfimages/default-source/blogs/2018/2018-11/state-of-js-2018/img-5.png?sfvrsn=5e92d879_2)

### Findings behind Salary

Why are less popular frameworks higher paying? I suspect it has something to do with supply and demand. If not many devs _like_ programming in a certain framework, then demand(and therefore salary) should be higher for them.

Also, side note, WHO ARE THESE PEOPLE?

[![screenshot of the second to last row in the chart highlighting 'I work for free'](https://www.telerik.com/sfimages/default-source/blogs/2018/2018-11/state-of-js-2018/img-6.png?sfvrsn=2eeb6a7a_2)](https://www.telerik.com/sfimages/default-source/blogs/2018/2018-11/state-of-js-2018/img-6.png?sfvrsn=2eeb6a7a_2)

I’m surprised there are so many people working for free, even if it’s only about a 1,000 people in total. I hope with all my heart these are people working on open source projects or non-profit type work. What we do as developers is valuable and I hope even the newest of devs know this.

## Company Size for Frameworks in 2018

[![chart showing company sizes for Vue.js, Ember, React, Preact, Angular, Polymer](https://www.telerik.com/sfimages/default-source/blogs/2018/2018-11/state-of-js-2018/img-7.png?sfvrsn=d5b3b683_2)](https://www.telerik.com/sfimages/default-source/blogs/2018/2018-11/state-of-js-2018/img-7.png?sfvrsn=d5b3b683_2)

Another unsurprising result is the two leading frameworks for largest company size — Polymer and Angular. This doesn’t surprise me because both of them are created, maintained, and tested by a ginormous company, Google. So it only makes sense that when other large companies/teams look to what Framework to use, they would choose one that is created/tested by an equally large company.

## Angular Results

### Most Liked/Disliked Aspects of Angular

It seems Angular is most liked for being full-featured & powerful and for having good documentation. Whereas, it is disliked most for being too bloated & complex with a hard learning curve. React was also disliked for it’s hard learning curve, whereas Vue.js was the only one greatly liked (voters in the thousands) for it’s easy learning curve.

[![screenshot of both likes and dislikes chart for Angular](https://www.telerik.com/sfimages/default-source/blogs/2018/2018-11/state-of-js-2018/img-8.jpg?sfvrsn=90c88324_2)](https://www.telerik.com/sfimages/default-source/blogs/2018/2018-11/state-of-js-2018/img-8.jpg?sfvrsn=90c88324_2)

Again, these findings don’t surprise me at all. I think with a larger ecosystem and full-featured framework, a harder learning curve is going to come with it. I love that good documentation was one of the other top things Angular is liked for. Good documentation is one of the best ways to combat a difficult learning curve.

## Findings Overall — Conclusion

The conclusions drawn for Angular weren’t as sunny as one might hope.

[![screenshot of overall conclusions chart in js survey 2018](https://www.telerik.com/sfimages/default-source/blogs/2018/2018-11/state-of-js-2018/img-9.png?sfvrsn=c6531428_2)](https://www.telerik.com/sfimages/default-source/blogs/2018/2018-11/state-of-js-2018/img-9.png?sfvrsn=c6531428_2)

> The other story of those past couple years is the fall of Angular. While it still ranks very high in terms of raw usage, it has a fairly disappointing 41% satisfaction ratio. So while it probably isn't going anywhere thanks to its large user base, it's hard to see how it will ever regain its place atop the front-end throne. - State of JS 2018

This prediction seems a bit too bleak for a couple of reasons. It’s true that Angular won’t be going anywhere because of its huge user base, however, I believe because of the [steady pace](https://dev.to/progresstelerik/whats-new-in-angular-7-24b2) Angular is trodding and the [future plans](https://www.telerik.com/blogs/first-look-angular-ivy) they have laid out, we could be on track for a throne toppling in the upcoming years.

I also think it is unfortunate that the survey has looped AngularJS and Angular together for this year and all upcoming years in the survey.

[![screenshot of quote from survey site: ‘Note that from this year on, we will not be making a distinction between Angular and Angular.js.’](https://www.telerik.com/sfimages/default-source/blogs/2018/2018-11/state-of-js-2018/img-10.png?sfvrsn=b81c25f9_2)](https://www.telerik.com/sfimages/default-source/blogs/2018/2018-11/state-of-js-2018/img-10.png?sfvrsn=b81c25f9_2)

AngularJS is a totally different framework from Angular and I believe its users will have drastically different concerns and happiness levels. Because of this, I really don’t know how accurately we can take the Angular findings from this survey.

## Developer Happiness

[![chart showing developer happiness with frameworks for 2016, 2017, and 2018](https://www.telerik.com/sfimages/default-source/blogs/2018/2018-11/state-of-js-2018/img-11.png?sfvrsn=6e131381_2)](https://www.telerik.com/sfimages/default-source/blogs/2018/2018-11/state-of-js-2018/img-11.png?sfvrsn=6e131381_2)

It seems, we as developers, are happier than we have been in the past two years, with the state of JS Frameworks. It could be that things are leveling out for us as a JS community. If you are one of the people who are still unhappy, though, the problem could be your job and not the framework you are working with.

I’ll pass on some million dollar advice I received from a friend in the industry, [Sharon Dio](https://twitter.com/sharondio). If you are unhappy in your job, take two weeks to analyze why. Write down everything you can think of during those two weeks that you enjoy or despise, no matter how trivial these items may seem. (For instance. checking company emails, styling UI, or even where my desk is at in the office.) Once you’ve made your lists, then the hunt begins. Start looking for companies that are doing the things on your enjoyment list. Even if they aren’t hiring at the time, send them an email with your resume and explain _why you are seeking them out_ and _how their values align with your own_.

I hope this advice helps, even if it means you move away from Angular (my true love). If it means there are happier, more productive devs in our community, I’ll take it as a win. I hope you all have a wonderful week, whether or not you are celebrating Turkey Day and happy coding!