链接到某一部分JavaScript/TypeScript 平衡
We're now firmly in the TypeScript era. 67% of respondents stated they write more TypeScript than JavaScript code – while the single largest group consisted of people who only write TypeScript.
链接到某一部分Compiled Code Balance
It should come as no surprise that in 2024, almost all of our JavaScript code goes through a build step. While bundlers and build tools certainly add complexity to our development process, they are most likely here to stay.
链接到某一部分AI Code Generation
For all the talk of AI-assisted coding, most of us still only use AI tools sparingly. And in fact, a whole 20% do not use them whatsoever to produce code.
链接到某一部分JavaScript 使用情况
It's always good to know in what context respondents are writing JavaScript code, and the vast majority are using it as part of their day job.
链接到某一部分JavaScript 使用情况
Virtually every respondent stated that they use JavaScript for frontend development, which makes sense given the language's origins.
链接到某一部分行业
While the largest industry sector consisted of developers building tools for other developers, the highest-paying one turned out to be Advertising.
链接到某一部分应用范式
Despite modern JavaScript meta-frameworks now supporting intricate rendering strategies, the most common application patterns remained the most traditional ones: single-page apps and server-side rendering.
链接到某一部分JavaScript 痛点
Code architecture is always a concern once a codebase gets past a certain size, so it makes sense that it topped the rankings of overall JavaScript pain points, followed by state and dependency management.
链接到某一部分New Proposals
There are currently quite a few TC39 proposals that are on the verge of becoming a reality. Temporal and Decorators stood out this year as the ones respondents were most excited about.
链接到某一部分缺失的功能
While the lack of native static typing has long been felt by the community, it's interesting to see Signals making an entrance at number 3 on this list, despite not being part of the most popular front end framework.
链接到某一部分Native Types
It's clear that survey respondents want native types, and that they hope to seem them implemented with a TypeScript-like syntax.
This year's question phrasing sadly did not make a clear distinction between runtime types and TypeScript-like type-as-annotations, so it remains to be seen which of these two paths will gain the community's favor.