So let's now move on to the state of React results themselves. And 7,870 respondents to the survey, which is quite a decent sample size. As one might expect, a lot of the respondents came from the US, but also European countries and overall a nice spread of respondents throughout the world.
One thing that's interesting, I think, is looking at years of experience. If you group those first two buckets, you actually see that 59% of respondents have less than 10 years of experience. In other words, they never knew a world where React didn't exist, in terms of them being web developers.
And so maybe for a lot of people taking the survey or even watching this, while React might seem like a very default way of doing things, very obvious. But if you have been around for longer than that, then you remember that when React was first introduced, it was actually quite innovative. Things like JSX, the virtual DOM, and even later on hooks, every time React did things a bit differently from everybody else.
We can also look at job titles. We have a good split between software engineer, developer, front-end developer. But it becomes really interesting when you switch to job titles versus income. Because here, you can see that engineer job titles, senior engineer, front-end engineer, are all at the top, whereas developers, front-end, full stack are at the bottom, with a pretty sizable gap in income between them.
And so, I don't know if this is correlation or causation, but just to be safe, if you're able to, I would recommend updating your resume if you are currently labeling yourself as a developer of some kind, and just replace that with engineer. Who knows, you might get a nice raise for your next position. Moving on to features.
So, let me explain how to read this chart, because I know it can be a lot to take in at first. For example, if we look at create portal here, you'll see that each row is split into three colored bars. The first one, dark blue, corresponds to users who have actually used a feature. Light blue is for users who have heard of a feature but not used it. And finally, gray is for users who haven't even heard of the feature. And then within those bars, you further have a subdivision according to positive sentiment in green and negative sentiment in red.
And then, in the middle, it's just people who didn't submit a sentiment, so who remained neutral. Now, what's cool about this system is you can change the grouping from experience to sentiment, and then you can also sort by, for example, positive sentiment. At the top here, we have things like fragment, create context, use states. In other words, APIs that are fairly straightforward to use, that are well understood, and those are the ones with very little negative sentiment.
But of course, you're probably curious to sort by negative sentiment and see which APIs are the most hated. And no surprise here, but forward ref is first by far.
Comments