4 ms·
The State of JavaScript 2017 survey is now open
- tyrw 9y agoI think I got all of them right, but frustrating that it doesn't let you know at the end.
- bjpbakker 9y agoIronically this survey does not work when javascript is disabled :)
- CharlesW 9y agoIt'd be ironic if it didn't work when JavaScript was enabled — this seems pretty on-brand. ¯\_(ツ)_/¯
- Sir_Cmpwn 9y agoThis needs a "Heard of it and don't have an opinion" option.
- iliketosleep 9y agoI agree. It's almost like there's a new JS fad every month and it's almost impossible to have an informed opinion on each of them.
- inimino 9y agoThat would be the "not interested" option, if you're not actively interested in learning it. There's not time for everything.
- acdha 9y agoThe other one I wanted was “Heard of it, but it's not relevant to my current projects” – “want to learn” overstated my level of interest in some cases.
- nailer 9y agoYeah same. Locally offline DBs that seamlessly sync to remote DBs and optimistically respond are cool, but not relevant to what I do now.
- altotrees 9y agoTook it, always mind-boggling how many new flavors and frameworks are coming out. Can't keep up! clojurescript, Typescript and vanilla js for me, all day long. Want to get into Elm also.
- acdha 9y agoAny survey like this should include at least one fake framework name to see which percentage of respondents aren't really reading the questions — but they'd probably have to preregister it on NPM to avoid someone publishing it as a joke.
- nailer 9y agoES5 and ES6/2015 options, but no ES8/2017? My code is requires 'await' and is significantly better for doing so. Since it covers SASS/CSS too, would be interested in % of people using grid or flexbox.