State of JS

State of JS
Name	State of JS
Developer	Sacha Greif
Released	2016
Language	English

State of JS.

The State of JS is an annual community survey and report focused on JavaScript toolchains, libraries, and developer sentiment. It summarizes adoption, satisfaction, and trends among practitioners associated with projects like React (JavaScript library), Vue.js, Angular (web framework), Node.js, and platforms such as GitHub and npm (software) while intersecting with ecosystems around TypeScript, Webpack, Babel (software), and cloud providers like Amazon Web Services, Microsoft Azure, and Google Cloud Platform. The survey influences discussion among contributors to ECMAScript, maintainers of jQuery, and participants in conferences such as JSConf, ng-conf, and React Conf.

Overview

The report compiles community responses about libraries, frameworks, build tools, testing frameworks, state management, and runtime environments; it references experiences with Express.js, Koa (web framework), Deno (software) experiments, and frontend frameworks tied to projects like Svelte, Preact, Ember.js, and Backbone.js. Respondents often cite integrations with services such as Docker, Kubernetes, Heroku, Netlify, and developer tools from JetBrains, Visual Studio Code, and Atom (text editor). Major open source organizations including the Linux Foundation, OpenJS Foundation, Mozilla Foundation, and companies like Facebook, Google, Microsoft, Twitter, Netflix, and Airbnb are frequently mentioned in relation to ecosystem health.

History and Development

Created in 2016 by Sacha Greif, the survey emerged as part of a broader set of developer surveys alongside efforts like the Stack Overflow Developer Survey and reports produced by firms such as RedMonk, Gartner, Forrester Research, and IDC. Early editions documented transitions from libraries maintained by teams at jQuery Foundation and Dojo Toolkit to modern component-driven development popularized by Facebook and community projects like OpenJS Foundation initiatives. Over successive years the report expanded to cover build tooling evolutions tied to Grunt (software), Gulp (software), Rollup (module bundler), and package management shifts from Bower (software) to Yarn (software) and pnpm alongside npm (software).

Survey Methodology

The project collects self-reported data via online forms distributed through channels such as Twitter, Reddit (website), Hacker News, Dev.to, and mailing lists associated with organizations like ACM and IEEE Computer Society. Respondent demographics reference employment at companies including IBM, Oracle Corporation, SAP SE, LinkedIn, and startups backed by firms such as Sequoia Capital and Andreessen Horowitz. Question design considers metrics familiar to researchers at Pew Research Center and statisticians at universities like Massachusetts Institute of Technology, Stanford University, and University of California, Berkeley. Analytic methods borrow practices from academic venues such as SIGPLAN, CHI, and datasets used in papers presented at ICSE and FSE.

Key Findings and Trends

Reports consistently highlight growth in TypeScript adoption, increasing use of component libraries like Material-UI, Ant Design, and rising interest in meta-frameworks such as Next.js and Gatsby (software). They document migration patterns from monolithic stacks to microservices associated with Docker and orchestration via Kubernetes, and note testing preferences involving Jest (JavaScript testing framework), Mocha (software), and Cypress (software). The surveys track developer sentiment around progressive enhancements such as Service Worker adoption, WebAssembly, and performance optimizations linked to V8 (JavaScript engine) and SpiderMonkey. Trends echo shifts observed around standards bodies like TC39 and implementations in browsers from Google Chrome, Mozilla Firefox, Apple Safari, and Microsoft Edge.

Impact on the JavaScript Ecosystem

The report shapes priorities for maintainers of ecosystems tied to npm (software), influences documentation improvements in projects hosted on GitHub, and informs product roadmaps at companies like Stripe, Shopify, Atlassian, Square (company), and GitLab. Conference talks at JSConf EU, React Europe, and meetups organized by Women Who Code and FreeCodeCamp often cite report findings to justify curriculum changes or community initiatives. Funders and venture firms reference adoption metrics in due diligence alongside technical signals from projects under the OpenJS Foundation and Node.js Foundation.

Criticism and Limitations

Critiques point to self-selection bias similar to concerns raised about the Stack Overflow Developer Survey and commercial reports from Gartner; sampling skew towards English-speaking regions including United States, United Kingdom, Canada, Germany, and India is noted. Methodological limitations mirror issues flagged in studies by ACM SIGMETRICS and IEEE workshops: small sample sizes for emerging projects like Deno (software) or niche libraries, ambiguity in question phrasing, and the challenge of mapping package usage from registries such as npm (software), Maven Central, or PyPI.

Reception and Influence on Industry Practices

Adopters among corporate engineering teams at Facebook, Google, Microsoft, Amazon (company), Netflix, and Airbnb use results to inform hiring, training, and technology choices; startup CTOs and developer advocates at firms backed by Sequoia Capital or Benchmark (venture capital) cite the report in blog posts on platforms like Medium (website) and Dev.to. Academic researchers referencing community surveys in venues such as ICSE, FAccT, and CHI have discussed the report when analyzing ecosystem dynamics. Despite criticisms, the annual publication remains a touchstone for conversations involving ECMAScript, browser vendors, open source foundations, and developer communities worldwide.

Category:JavaScript