What Front‑End Tools Do Developers Really Use? 2016 Survey Insights

Lies, Damned Lies, and Statistics: Front‑End Survey Overview

"Lies, damned lies, and statistics" is a famous Western proverb describing the persuasive power of numbers, often used to mock dubious statistical claims.

The survey collected 5,254 responses, providing a sizable sample, but the results should be interpreted cautiously.

Global Results

The questionnaire was global but primarily English‑speaking, so tools popular elsewhere may be under‑represented.

Developer Experience

83% of respondents have two or more years of front‑end experience, while only 5% have less than one year.

Developers with lower front‑end skills are less likely to complete the survey, potentially biasing the results.

Opinions and Bias

Self‑assessment can be skewed: some respondents are modest, others may overestimate their abilities, especially when they are the sole front‑end developer on a team.

Past Behavior Not Future Trend

The survey highlights tools currently in use, but this does not guarantee they will remain useful or be adopted in future projects.

CSS

63% of developers rate their CSS knowledge as advanced or expert.

CSS may seem simple, but mastering CSS3 features, Grid, and Flexbox can be challenging.

Author note: Recommended reading – CSS3 Flexbox visual guide.

10% of respondents with less than one year of experience claim advanced CSS knowledge, suggesting a gap between confidence and competence.

CSS Preprocessors

Over 63% use Sass, 8% use PostCSS (often together with AutoPrefixer, adopted by 65%).

Nearly 14% avoid preprocessors, preferring raw CSS.

About 70% have tried Less, 19% tried Stylus, and 80% have never heard of Rework.

CSS Naming Conventions

46% of developers use a naming scheme; this rises to 57% among those rating themselves as advanced or expert.

The most popular is BEM (40%), followed by CSS Modules (16%), OOCSS (15%) and SMACSS (13%).

Other CSS Tools

39% of projects use Modernizr, primarily for legacy IE compatibility.

14% use Stylelint for CSS validation; 23% use no CSS tooling or naming scheme.

JavaScript

51% of respondents consider their JavaScript knowledge advanced or expert.

Libraries and Frameworks

More than 99% have used jQuery; 31% deem it necessary, and 70% still use it in current projects.

Framework adoption is mixed: 38% of projects use React (29% comfortable, 18% consider it necessary), 25% use Angular 1 (8% see it as indispensable), Angular 2 sees minimal use, and Vue.js appears in 10% of projects (under 6% feel comfortable).

Only 21% think frameworks are unnecessary and prefer native code; 30% believe their framework skills cover all needs.

Task Runners and Bundlers

Gulp is the top task runner (44%); npm scripts have grown to 26%. Grunt has fallen to 12%, and 9% use no task runner.

Author note: See articles “Why I Dropped Gulp and Grunt for npm Scripts” and “Why Use npm Scripts to Build Projects”.

Bundler usage increased by 20% to 68%; Webpack leads with 31%, followed by Browserify (11%) and RequireJS (8%).

Transpilers

62% use Babel to convert ES6 to ES5; 31% have heard of transpilers but do not use them, and 7% have never heard of the term.

While older browsers lack ES6 support, many developers still target ES5 for compatibility.

Other JavaScript Tools

41% use ESLint, 19% JSLint, 14% JSHint; 23% do not use any linting tool.

Testing tool usage rose to 52%; popular frameworks include Mocha (23%), Jasmine (17%), QUnit (4%), Jest (3%) and Ava (2%).

94% use npm, and surprisingly 32% have tried TypeScript.

What Should You Use in 2017?

For CSS, knowledge of Sass, PostCSS and BEM is essential; exploring preprocessors and naming schemes is recommended.

In JavaScript, Node.js and npm are indispensable, Gulp and/or Webpack are worth trying, and learning ES6 is valuable even when targeting ES5.

jQuery remains popular but its relevance declines as IE usage drops; choose frameworks like React wisely, but prioritize solid fundamentals in HTML, CSS, JavaScript, and browser development.