1. 12
    State Of JavaScript Survey Results javascript stateofjs.com
    pushcx avatar via pushcx 1 year ago | cached | 1 comment

  1.  

  2. 2
    wambotron avatar wambotron 1 year ago | link

    I work in JavaScript every day at work and usually a good bit in my personal time as well, so you may or may not be interested in my answers.

    Flavors
    • Plain JS: Use/will continue
    • ES6: Use/will continue
    • Coffeescript: Used in the past, will not use again.
    • Typescript: Heard, not interested
    • Elm: Heard, not interested
    • Clojurescript: heard, not interested
    Front-end Frameworks
    • None: Use/will continue
    • React: Heard, somewhat interested
    • Angular: Used, will not use again
    • Angular 2: Heard, somewhat interested
    • Ember: Heard, not interested
    • Vue: Heard, not interested
    • Backbone: Used, will not use again
    • I use Mithril at work and I find it incredibly easy. Source is about 1k lines total. Docs are good. I’d recommend it.
    State Management
    • Redux: Heard, interested
    • Mobx: Never heard of it
    • Relay: Never heard of it
    API Layers
    • REST API: Use/will continue
    • Firebase: Heard, not interested
    • GraphQL: Never heard of it
    • Apollo: Never heard of it
    • Falcor: Never heard of it
    • Horizon: Never heard of it
    Full Stack
    • Meteor: Heard, not interested
    • FeathersJS: Never heard of it
    • DoneJS: Never heard of it
    • MERN: Never heard of it
    • MEAN: Used, will not use again
    Testing
    • Mocha: Use, will continue
    • Jasmine: Use, will continue
    • Enzyme: Never heard of it
    • Jest: Use, will continue
    • Cucumber: Used, will not use again
    • Ava: Never heard of it
    CSS
    • Plain CSS: Use/will continue
    • SASS/SCSS: Used, will not use again
    • LESS: Used, will not use again
    • CSS Modules: Never heard of it
    • Aphrodite: Never heard of it
    • I use Stylus since I’m already in an all-JS environment. I like it just fine
    Build Tools
    • Webpack: Heard, interested
    • Grunt: Use, will continue
    • Gulp: Heard, not interested
    • Browserify: Use, will continue
    Mobile Frameworks

    Skipping this section since I do no mobile-only dev

    Features
    • Server-side rendering: Depends on the use case. Internal tool? Not needed. Regular ol' page? Vital feature
    • Code-splitting: Nice to have
    • Optimistic updates: Nice to have
    • Hot module reloading: Nice to have
    • Time-travel Debugging: Nice to have
    • Real-time operations: Nice to have
    • Dead code elimination: Realistically nice to have, but oh how I wish it were vital
    • Progressive enhancement: Vital feature
    Opinions
    • Building js applications is overly complex right now: Generally agree (4)
    • JS is over-used online: Agree (5)
    • The JS ecosystem is changing too fast: Neutral (3)
    • I would like JS to be my main language: Neutral (3) – it is my main language, but I am ok with a multitude of others being the main language
    • JS is moving in the right direction: Neutral (3) – There are things I like and things I dislike, but I can adapt to whatever
    • I enjoy building JS apps: Agree (5)
    Years of Experience

    10-20 years

    Yearly Salary

    100-200k

    Favorite Text Editor

    VS Code followed very closely by Webstorm