Earlier in the year, I posted on DesignerNews asking for people to take part in this year's Front-end Tooling Survey – I've now (finally!) written up the results so I wanted to share them here for anyone that took part, or that may be interested in the results.

I'd love to hear people's thoughts on the results – and if anyone has any questions or comments about the survey, I'd love to hear them and I'll make sure I answer questions in the comments.

Thanks!

Sorry for delayed reply - missed some of my notifications!

I try and keep the options minimal and then if a tool get's enough mentions under 'Other' I break it out in the results and include it in future surveys. Elm has had a few mentions so may look to break that out as an option in future for sure :)

No problem – thanks for taking part!

Will take a look at revising this in future survey's as I've had this feedback in relation to testing tools previously. Would be good to know which combinations people are using together for sure.

Thanks for the feedback.

Thanks – appreciated!

We’d definitely be open to work on that – plans for the framework are pretty flexible really (mainly shaped by advances in CSS/JS), so including more layout options leveraging Flexbox certainly makes a lot of sense.

I’ll make sure we add it to our issues to discuss.

All fair points – I was simply trying to strike the balance between getting useful info and not asking too many questions. What popular tools were left out of any questions?

Also, having jQuery and Angular in the same question was to judge knowledge levels, not to provide a comparison between the two functionally.

I am going to try to run the survey periodically to see if trends emerge, so will look at adjusting the questions slightly to gain as much value as possible. Thanks for the feedback!

Thanks for taking the survey – appreciated :)

My reasons for running it are similar – I want to find out more about current knowledge levels of the most popular frameworks and tools. I completely agree with your point on imposter syndrome – it’s easy to feel like you’re constantly behind the curve, when in reality (by way of using DesignerNews and other similar resources) you’re more likely to be ahead of where a lot of FE devs are in terms of knowledge.

The idea of PostCSS is that it can be as simple or complex as you like. If there’s only one feature you want to add to your standard CSS, you can just add that, rather than having a whole heap of other features you don’t need too.

Mostly intended as a link-bait title, rather than a serious judgement!

Sass is going nowhere anytime soon, but I do think PostCSS offers an interesting alternative that could be quite powerful. It definitely won’t be gone in 2 weeks ;)