The State of JavaScript 2018
2018.stateofjs.com
The State of JavaScript 2018
1–10 of 286 posts
Re: The State of JavaScript 2018
#2(As long as the question is not something along the lines of "My favorite library Foo.js is doing pretty poorly in your survey, surely there must be an issue with your methodology?")
Re: The State of JavaScript 2018
#3Co-author of the survey here, thanks for posting! Happy to answer any questions :) (As long as the question is not something along the lines of "My favorite library Foo.js is doing pretty poorly in your survey, surely there must be an issue with your methodology?")
Re: The State of JavaScript 2018
#4Re: The State of JavaScript 2018
#5Re: The State of JavaScript 2018
#6Co-author of the survey here, thanks for posting! Happy to answer any questions :) (As long as the question is not something along the lines of "My favorite library Foo.js is doing pretty poorly in your survey, surely there must be an issue with your methodology?")
Re: The State of JavaScript 2018
#7Co-author of the survey here, thanks for posting! Happy to answer any questions :) (As long as the question is not something along the lines of "My favorite library Foo.js is doing pretty poorly in your survey, surely there must be an issue with your methodology?")
Re: The State of JavaScript 2018
#8Re: The State of JavaScript 2018
#9Ouch, the ratio of "would use again" to "would not use again" on AngularJS stunning, if not surprising: https://2018.stateofjs.com/front-end-frameworks/overview/
Re: The State of JavaScript 2018
#10Co-author of the survey here, thanks for posting! Happy to answer any questions :) (As long as the question is not something along the lines of "My favorite library Foo.js is doing pretty poorly in your survey, surely there must be an issue with your methodology?")
Anyone doing a state of any language/platform should take note.