[State of JS 2019] Question Outline about stateofjs-legacy

[pixlforge]

Would it make sense to add Nuxt and Next to the list of frameworks?

[manniL]

Maybe it'd be worth asking if one is using a meta framework (e.g. Nuxt.js for Vue, Next for React, Sapper for Svelte etc.)? I'd be eager to know how many devs use such a meta framework (or app framework) instead of relying on a component-level framework "only".

[TheJaredWilcurt]

Super happy to see NW.js added 🎉, but a little surprised to see NativeScript being removed. NativeScript-Vue has really taken off in the last year. It's become the go-to recommendation for the Vue community; and seems to be doing a lot more innovation around code sharing than anything else in that space.

The example of having the templates for web and mobile kept in the same .vue file and reusing the shared logic between the two UI's just seems like a really intuitive approach to building and maintaining both:

[SachaG]

@S1ngS1ng those are all great suggestions! I can't change the survey now that it's live but I'll take them into account for next year.

[SachaG]

Oh and regarding translations, we didn't really have time to think about it this time but now that our infrastructure supports it since we're using our own platform, it's definitely something I want to do next time.

[SachaG]

Would it make sense to add Nuxt and Next to the list of frameworks?

We originally had Next in the Back-End section, but we decided to drop it. But yes if we still had it we'd probably add Nuxt, too.

[BBlackwo]

Interesting you decided to drop Jasmine. It's still quite popular https://www.npmtrends.com/jasmine-vs-jest-vs-ava

Great move to add Cypress!

[akiroussama]

Flutter in web technology?

[SachaG]

@akiroussama does Flutter have anything to do with JavaScript though?

[orta]

@SachaG a lot people of see Dart as a competitor to JS from the context of React Native vs Flutter - I think it's reasonably big FWIW but maybe not big enough for inclusion

I wondered about the "Build Tools" section. It could probably be split into "bundlers" and "build tools" (as there's only one thing that's not really a bundler in there)

Bundlers

• Webpack
• Parcel
• Rollup
• FuseBox

Build Tools

• gulp
• eslint
• prettier
• tslint
• lerna
• yarn workspaces

for example

---

Syntax: Could add optional chaining, import/export also

[dcorb]

would you consider lit-html the successor of Polymer? Although it's not a framework, people could be interested to track web components usage.

And I think it's probably a mistake to drop the "backend" section. Tracking the JS ecosystem without nodejs or SSR solutions feels very wrong to me. It's one of the most interesting parts of State of JS. I would drop "other languages" section if you want to keep it shorter

[S1ngS1ng]

Hey Sasha, I got a few suggestions here:

1. It might make sense to include Prototype Design Pattern under "Patterns".
2. +1 for Optional Chaining and import/export. Both are a good fit under "Syntax".
3. The order of options seems a little bit weird to me:
   
   Personally, I consider that the "Heard of it > Not interested" should come before "Heard of it > Would like to learn". What's your opinion?
4. It is good to see "Podcasts" under "Resources". For Syntax, it might be better to name it more specifically as Syntax.fm. Plus, here are some other podcasts that I'd recommend including:
   1. Toolsday
   2. Base.cs Podcast
   3. Command Line Heroes
   4. Developer Tea
5. EDIT: Just noticed that it is under "Magazine". But it might be better to have a new sub-category named a "newsletter"? What's your opinion? The newsletter regarding dev topics has been popular. Personally, this is one of my primary go-to resources to explore something new. I'd recommend including those newsletters, just to name a few:
   1. JavaScript Weekly
   2. ES.next News
   3. Web Tools Weekly
   4. Node Weekly
   5. Frontend Focus
   6. React Status
   7. Angular Weekly
      =========
   8. CSS Weekly
   9. Web Design Weekly
   10. CSS Animation Weekly
6. EDIT: Just noticed that Dev.to is included. Again, what's your opinion of adding a sub-category of "Community"? I'd propose adding another sub-category under "Sources", that is Community. Though sometimes, it might be considered as part of "Sites & Courses" as well. To name a few:
   1. Dev.to
   2. freeCodeCamp forums
   3. Reddit (🤦‍♂)

And a question, are we planning on the translation for this year? I could help with Chinese.
Another thing is, AFAIC, there are MANYYYY other resources/sites/... that are popular specifically within the Chinese developers' community. It might be beneficial that we include those while working on the translation. But that could be way too much overhead, which makes the statistics to be more complex.