JavaScript developers feel the language is moving in the right direction • The Register

The State of JavaScript 2021 survey has arrived, a little later than expected (no jokes about language performance, please) and following a somewhat embarrassing data leak.

The 2020 State of JavaScript report is based on a survey of 23,000 developers. 2021 was the result of just over 16,000. And although the United States was in the lead, its share of survey respondents fell to 14% and Russia climbed to third place behind Germany with 4 %.

Unfortunately, the vast majority (93.2%) of those who answered the gender question said they were male, up from 91.1% last year. 82.4% chose to complete the survey in English. JavaScript may be impressively diverse from a technological standpoint, but the same cannot be said for the respondents to this survey.

However, JavaScript remains by far the most popular language among developers, recording nine years as the most commonly used language in the Stack Overflow survey. The trends in its ecosystem are therefore very significant.

In terms of frameworks and libraries, React continued to lead in usage, followed by Angular and Vue.js. React is also at the top of the awareness rankings, but its satisfaction drop is marked, with the library now ranking third as interest waned, placing React fourth behind Vue.js, Solid and Svelte. Solid came in first for satisfaction and second for interest, although it was second from the bottom in terms of people actually using it (behind Alpine.js and Ember).

The majority of respondents think the language is “moving in the right direction” and there was a slight drop in the proportion who felt that building apps was too complex.

As for what was missing, static typing remained at the top of the charts, although a majority of respondents said they were “satisfied” or “very satisfied” with the overall state of JavaScript and web technologies in general. With 22% of those answering the salary question wearing pants of $100,000 to $200,000 a year, we can’t really blame them.

And the data leak? An encryption key to decrypt publicly accessible encrypted email addresses and link them to survey responses was accidentally left on a public GitHub repository. Whoops!

Table drilling system

Book a table. 1 credit

Yet, as the example pictured above of a table reservation system (borking?) shows, it’s all too easy for web technologies to get a little wrong in very public ways. ®

Comments are closed.